On 2016/4/15 18:43, Paolo Bonzini wrote:
On 15/04/2016 12:37, Yang Zhang wrote:
I don't think this is performance-sensitive, hence it's simpler to keep
the code as simple as possible. For example, if one added XSETBV
support to the emulator, your patch would introduce a bug.
In what case we need to decode XSETBV?
The emulator can be a way to unify code between vmx and svm. It is an
alternative to writing small wrapper functions such as kvm_set_xcr.
I still think the correctness is important. But it's ok to leave it
there since it doesn't cause any real problem so far. :)
--
best regards
yang
--
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
