On 04/11/2019 09:29 AM, Sean Christopherson wrote:
On Thu, Apr 11, 2019 at 02:14:35PM +0200, Paolo Bonzini wrote:
On 11/04/19 02:15, Krish Sadhukhan wrote:
May be we should also rename its counterpart
(i.e.,nested_vmx_check_vmentry_prereqs) to something like
nested_vmx_check_vmentry_pre_guest_state or something similar ?
I think we should have three functions
nested_vmx_vmentry_check_{controls,host_state,guest_state}.
Four if you count nested_vmx_load_msr(). But anyways, I agree.
On a related subject, an invalid guest activity state results in a VM-Exit,
not VM-Fail, i.e. nested_check_guest_non_reg_state() belongs in
nested_vmx_check_vmentry_postreqs().
That's correct !
Moving that code to its proper
location would eliminate the last odditiy for renaming "postreqs" to
nested_vmx_vmentry_check_guest_state().
I'll send a series, including patches 1 and 2 (the PAT checks) from
Krish's series?
Sounds good. Thanks.
