I don't like this change. It's not bad code, but it'll be confusing because itHonestly I don't see how you had reached this conclusion.
implies that it's legal for svm->vmcb to be something other than svm->vmcb01.ptr
when this is called.
I just think that code that always works on vmcb01
should use it, even if it happens that vmcb == vmcb01.
If you insist I can drop this patch or add WARN_ON instead,
I just think that this way is cleaner.