On 12/01/2010 11:27 AM, Nadav Har'El wrote:
I really want to get nested VMX into KVM, and I'm already doing whatever I can to make this a reality. But unfortunately, I am not yet a seasoned KVM or VMX expert (I'm trying to become one...), and it wasn't I who wrote the original nested VMX code, so every new issue and every new feature that I am asked to fix is new to me, and takes me considerable time to learn, debug, and fix. I hope to continue working on nested VMX, next year as well, but IBM's (my employer's) plans for next year are not yet set in stone. In any case, I firmly believe that the nested VMX feature will be better, and be available more quickly, if I am not the only person working on it. I will be very happy if somebody reading this wants to work on this with me. This is the main reason why I wanted to put nested VMX in the main tree (even before it is 100% bug-free and feature-complete), because that would make it much easier for more people to try this feature, and hopefully to help me fix problems which bother them.
I am reluctant to lower the bar on entry. Things like SMP and host EPT support are really basic IMO. Good integration into KVM is also important.
If you would like to get more people participating, I suggest publishing a git tree. People can then post patches against the tree, which you can merge into the relevant commits. It would also get more testing done by interested parties.
-- error compiling committee.c: too many arguments to function -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
