[Rust-VMM] RFC:

[Florescu, Andreea]

Hey,


It's not a big deal. We can review it from rust-vmm since it is already there. I would say not to publish it as a crate yet.


When migrating the repository (even if it's private) all discussions should also be migrated by default.


Andreea


________________________________
From: Liu Jiang <liuj97 at gmail.com>
Sent: Friday, February 8, 2019 2:45 PM
To: Florescu, Andreea
Cc: rust-vmm ML; Samuel Ortiz; Boeuf, Sebastien; Iordache, Alexandra; Dylan Reid; Dr. David Alan Gilbert
Subject: Re: [Rust-VMM] RFC:

Hey,
Sorry for break the process. Should I delete the repository from the rust-vmm project?
BTW, there may be some discussion threads when holding the library on private repository, so what's the best practice to preserve discussions on private repository when migrating from private repository to the rust-vmm project?
Thanks,
Gerry

On Feb 8, 2019, at 7:58 PM, Florescu, Andreea <fandree at amazon.com<mailto:fandree at amazon.com>> wrote:

Hey,

For future crates I would suggest we do not create repositories directly in the rust-vmm organization and use the review process we discussed a while back:
- Create a repository on the personal profile
- Request reviews for the repository using the issue template for reviews

This process is also described in the community readme: https://github.com/rust-vmm/community

Regarding the review, I might be able to look at the changes somewhere after Wednesday next week.

Regards,
Andreea

________________________________
From: Liu Jiang <liuj97 at gmail.com<mailto:liuj97 at gmail.com>>
Sent: Friday, February 8, 2019 12:17 PM
To: rust-vmm ML; Florescu, Andreea; Samuel Ortiz; Boeuf, Sebastien; Iordache, Alexandra; Dylan Reid; Dr. David Alan Gilbert
Subject: [Rust-VMM] RFC:

Hi all,
As we have discussed during the meeting, I have created a memory-model repository under rust-vmm project and  posted the initial version at https://github.com/rust-vmm/memory-model .
The initial version tries to merge current code from the upstream crosvm and firecracker projects. And the most sensitive user visible change is changing from u64 to usize for memory related data fields.
So please help to comment on whether this is the right way to go, and next step plan is:
1) import endian.rs<http://endian.rs/> from crosvm
2) add address space abstraction for virtual machine
Thanks,
Gerry

Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.




Amazon Development Center (Romania) S.R.L. registered office: 27A Sf. Lazar Street, UBC5, floor 2, Iasi, Iasi County, 700045, Romania. Registered in Romania. Registration number J22/2621/2005.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opendev.org/pipermail/rust-vmm/attachments/20190208/2beae67d/attachment.html>