On 2015-11-10 at 06:07 ron minnich <[email protected]> wrote: > I've been feeling for some time that we'd have to break out > applications for akaros from the akaros tree itself. It's a necessary > part of the maturation process; not every program should be in the > kernel source tree :-)
Agreed, in general, though I'm a little concerned about taking the VMM out, given the tight coupling of the VMM with the kernel. It's this same coupling that allows us to make changes to the kernel headers and glibc at the same time. We are far from having stable kernel interfaces, and I'm worried having a different repo will make things more difficult. If we make changes in Akaros to VMM code (such as the upcoming changes to treat VMs as just another type of context), how do we test this? Do we need to sync up between repos? > With that breakout would come the possibility of using a different > workflow for commits and reviews. I think you two could have been doing that already - using gerrit to manage virtio-r, but still as part of the main repo. Barret -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
