[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfYhtHS3d4m07+qAxPzdR_jZ4Q9OC9K=Tf4sviH1Nn5cyw@mail.gmail.com>
Date: Fri, 29 Sep 2023 19:42:05 +0200
From: Paolo Bonzini <pbonzini@...hat.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: Maxim Levitsky <mlevitsk@...hat.com>, kvm@...r.kernel.org,
iommu@...ts.linux.dev, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Borislav Petkov <bp@...en8.de>, Joerg Roedel <joro@...tes.org>,
x86@...nel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@....com>,
linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>,
Will Deacon <will@...nel.org>, Ingo Molnar <mingo@...hat.com>,
Robin Murphy <robin.murphy@....com>
Subject: Re: [PATCH v2 0/4] AVIC bugfixes and workarounds
On Fri, Sep 29, 2023 at 4:09 AM Sean Christopherson <seanjc@...gle.com> wrote:
>
> On Thu, Sep 28, 2023, Maxim Levitsky wrote:
> > Maxim Levitsky (4):
> > x86: KVM: SVM: always update the x2avic msr interception
> > x86: KVM: SVM: add support for Invalid IPI Vector interception
> > x86: KVM: SVM: refresh AVIC inhibition in svm_leave_nested()
>
> Paolo, I assume you'll take the first three directly for 6.6?
Yes.
Paolo
> > x86: KVM: SVM: workaround for AVIC's errata #1235
>
Powered by blists - more mailing lists