From: Greg KH <gregkh@linuxfoundation.org>
To: Yosry Ahmed <yosry.ahmed@linux.dev>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH 6.12.y 0/5] LBR virtualization fixes
Date: Fri, 21 Nov 2025 10:55:38 +0100 [thread overview]
Message-ID: <2025112118-everyone-perish-5a7a@gregkh> (raw)
In-Reply-To: <20251120233936.2407119-1-yosry.ahmed@linux.dev>
On Thu, Nov 20, 2025 at 11:39:31PM +0000, Yosry Ahmed wrote:
> This is a backport of LBR virtualization fixes that recently landed in
> Linus's tree to 6.12.y.
>
> Patch 1 is not a backport, it's introducing a helper that exists in
> Linus's tree to make the following backports more straightforward to
> apply.
Why not include the actual commit that adds that helper?
> Patch 2 should already be in queue-6.12, but it's included here as the
> remaining patches depend on it.
So this series will not apply?
confused,
greg k-h
next prev parent reply other threads:[~2025-11-21 9:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 15:50 FAILED: patch "[PATCH] KVM: nSVM: Always recalculate LBR MSR intercepts in" failed to apply to 6.12-stable tree gregkh
2025-11-20 23:39 ` [PATCH 6.12.y 0/5] LBR virtualization fixes Yosry Ahmed
2025-11-20 23:39 ` [PATCH 6.12.y 1/5] KVM: SVM: Introduce svm_recalc_lbr_msr_intercepts() Yosry Ahmed
2025-11-20 23:39 ` [PATCH 6.12.y 2/5] KVM: SVM: Mark VMCB_LBR dirty when MSR_IA32_DEBUGCTLMSR is updated Yosry Ahmed
2025-11-20 23:39 ` [PATCH 6.12.y 3/5] KVM: nSVM: Always recalculate LBR MSR intercepts in svm_update_lbrv() Yosry Ahmed
2025-11-20 23:39 ` [PATCH 6.12.y 4/5] KVM: nSVM: Fix and simplify LBR virtualization handling with nested Yosry Ahmed
2025-11-20 23:39 ` [PATCH 6.12.y 5/5] KVM: SVM: Fix redundant updates of LBR MSR intercepts Yosry Ahmed
2025-11-21 9:55 ` Greg KH [this message]
2025-11-21 15:17 ` [PATCH 6.12.y 0/5] LBR virtualization fixes Yosry Ahmed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025112118-everyone-perish-5a7a@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=yosry.ahmed@linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox