On 09/26/2010 04:28 PM, Nadav Har'El wrote:
> I'm worried about maintaining core vmx after nvmx is merged, not nvmx > itself. There are simply many more things to consider when making a change. Right, but how can we avoid this issue, assuming that you do want nvmx in?
We can't avoid it. We can mitigate it to some extent by structuring the code correctly.
May I ask how this effected nested SVM?
I kept breaking nsvm when making changes to core svm, and Joerg kept fixing them.
-- 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
