[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABgObfa8O9m+jFBMMnJn63PSnK8rQWixKH4WkcjKAh9F4UtzwQ@mail.gmail.com>
Date: Mon, 17 Nov 2025 19:38:09 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: Yosry Ahmed <yosry.ahmed@...ux.dev>
Cc: Sean Christopherson <seanjc@...gle.com>, kvm@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH] KVM: SVM: Fix redundant updates of LBR MSR intercepts
On Fri, Nov 14, 2025 at 5:52 PM Yosry Ahmed <yosry.ahmed@...ux.dev> wrote:
>
> On Fri, Nov 14, 2025 at 08:34:54AM -0800, Sean Christopherson wrote:
> > On Wed, Nov 12, 2025, Yosry Ahmed wrote:
> > > svm_update_lbrv() always updates LBR MSRs intercepts, even when they are
> > > already set correctly. This results in force_msr_bitmap_recalc always
> > > being set to true on every nested transition,
> >
> > Nit, it's only on VMRUN, not on every transition (i.e. not on nested #VMEXIT).
>
> How so? svm_update_lbrv() will also be called in nested_svm_vmexit(),
> and it will eventually lead to force_msr_bitmap_recalc being set to
> true.
>
> I guess what you meant is the "undoing the Hyper-V optimization" part.
> That is indeed only affected by the svm_update_lbrv() call in the nested
> VMRUN path.
Yes, I'll make sure that's clear in the changelog.
> Paolo, do you prefer a updated patch with the updated changelog, or
> fixing it up when you apply it?
I'll take care of it, thanks!
Paolo
Powered by blists - more mailing lists