[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zwm9isnme2YLcuhq@google.com>
Date: Fri, 11 Oct 2024 17:06:34 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: Ivan Orlov <iorlov@...zon.com>
Cc: bp@...en8.de, dave.hansen@...ux.intel.com, mingo@...hat.com,
pbonzini@...hat.com, shuah@...nel.org, tglx@...utronix.de, hpa@...or.com,
kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-kselftest@...r.kernel.org, x86@...nel.org, jalliste@...zon.com,
nh-open-source@...zon.com, pdurrant@...zon.co.uk
Subject: Re: [PATCH 1/3] KVM: x86, vmx: Add function for event delivery error generation
On Fri, Oct 11, 2024, Sean Christopherson wrote:
> > + kvm_x86_call(get_exit_info)(vcpu, &reason, &info1, &info2, &intr_info, &error_code);
>
> Wrap. Though calling back into vendor code is silly. Pass the necessary info
> as parameters. E.g. error_code and intr_info are unused, so the above is wasteful
> and weird.
Ah, but the next patch invokes this from common code, i.e. can't pass in the
necessary info. _That_ is definitely worth calling out in the changelog.
Powered by blists - more mailing lists