[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d385c639-d2b1-4068-b386-98c456265926@zytor.com>
Date: Fri, 28 Jun 2024 21:01:28 -0700
From: Xin Li <xin@...or.com>
To: Jacob Pan <jacob.jun.pan@...ux.intel.com>, X86 Kernel <x86@...nel.org>,
Sean Christopherson <seanjc@...gle.com>,
LKML
<linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Dave Hansen <dave.hansen@...el.com>, "H. Peter Anvin" <hpa@...or.com>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Xin Li <xin3.li@...el.com>, linux-perf-users@...r.kernel.org,
Peter Zijlstra <peterz@...radead.org>
Cc: Paolo Bonzini <pbonzini@...hat.com>, Tony Luck <tony.luck@...el.com>,
Andy Lutomirski <luto@...nel.org>, acme@...nel.org,
kan.liang@...ux.intel.com, Andi Kleen <andi.kleen@...el.com>,
"Mehta, Sohil" <sohil.mehta@...el.com>,
Zeng Guang <guang.zeng@...el.com>
Subject: Re: [PATCH v3 06/11] KVM: VMX: Expand FRED kvm entry with event data
On 6/28/2024 1:18 PM, Jacob Pan wrote:
> From: Zeng Guang <guang.zeng@...el.com>
>
> For VM exits caused by events (NMI, #DB, and #PF) delivered by FRED, the
> event data is saved in the exit-qualification field. (FRED spec. 10.6.2)
I don't like mentioning #DB/#PF here, they belong to the guest that was
running, and KVM handles them.
While NMIs belong to host, and the host NMI handler needs event data
saved in VMCS in NMI induced VM exits.
Or you paint a full picture.
> Expand FRED KVM entry interface to include the event data obtained from
> the exit qualification.
>
> Signed-off-by: Zeng Guang <guang.zeng@...el.com>
> Signed-off-by: Jacob Pan <jacob.jun.pan@...ux.intel.com>
Powered by blists - more mailing lists