[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMvTesB-vrPMDfGhPUb-0ntkCGdUKUtsWe=0PQ65zvbqTwko=g@mail.gmail.com>
Date: Tue, 15 Jul 2025 12:49:12 +0800
From: Tianyu Lan <ltykernel@...il.com>
To: Neeraj Upadhyay <Neeraj.Upadhyay@....com>
Cc: linux-kernel@...r.kernel.org, bp@...en8.de, tglx@...utronix.de,
mingo@...hat.com, dave.hansen@...ux.intel.com, Thomas.Lendacky@....com,
nikunj@....com, Santosh.Shukla@....com, Vasant.Hegde@....com,
Suravee.Suthikulpanit@....com, David.Kaplan@....com, x86@...nel.org,
hpa@...or.com, peterz@...radead.org, seanjc@...gle.com, pbonzini@...hat.com,
kvm@...r.kernel.org, kirill.shutemov@...ux.intel.com, huibo.wang@....com,
naveen.rao@....com, kai.huang@...el.com
Subject: Re: [RFC PATCH v8 19/35] x86/apic: Initialize Secure AVIC APIC
backing page
On Wed, Jul 9, 2025 at 11:40 AM Neeraj Upadhyay <Neeraj.Upadhyay@....com> wrote:
>
> With Secure AVIC, the APIC backing page is owned and managed by guest.
> Allocate and initialize APIC backing page for all guest CPUs.
>
> The NPT entry for a vCPU's APIC backing page must always be present
> when the vCPU is running, in order for Secure AVIC to function. A
> VMEXIT_BUSY is returned on VMRUN and the vCPU cannot be resumed if
> the NPT entry for the APIC backing page is not present. To handle this,
> notify GPA of the vCPU's APIC backing page to the hypervisor by using the
> SVM_VMGEXIT_SECURE_AVIC GHCB protocol event. Before executing VMRUN,
> the hypervisor makes use of this information to make sure the APIC backing
> page is mapped in NPT.
>
> Co-developed-by: Kishon Vijay Abraham I <kvijayab@....com>
> Signed-off-by: Kishon Vijay Abraham I <kvijayab@....com>
> Signed-off-by: Neeraj Upadhyay <Neeraj.Upadhyay@....com>
> ---
> Changes since v7:
> - No change.
Reviewed-by: Tianyu Lan <tiala@...rosoft.com>
--
Thanks
Tianyu Lan
Powered by blists - more mailing lists