From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, sashal@kernel.org, bp@alien8.de
Subject: Re: [PATCH v3 5.15.y 1/3] KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code
Date: Thu, 11 Sep 2025 11:40:26 -0400 [thread overview]
Message-ID: <ddbba881-5c51-464f-a41d-2ea39e0183b3@oracle.com> (raw)
In-Reply-To: <2025091158-cloak-murky-d3bd@gregkh>
On 9/11/25 8:33 AM, Greg KH wrote:
> On Tue, Sep 09, 2025 at 08:28:24PM -0400, Boris Ostrovsky wrote:
>> From: Kim Phillips <kim.phillips@amd.com>
>>
>> Commit c35ac8c4bf600ee23bacb20f863aa7830efb23fb upstream
>
> This isn't in 6.1.y, so backporting it only to 5.15.y feels "odd" and
> will trigger our scripts trying to figure out why.
>
> Why is only needed here? Things were fixed differently in 6.1.y, or is
> 6.1.y not affected here?
Hmmm... I think 6.1.y is broken as well, including the need for
f3f9deccfc68a6b7c8c1cc51e902edba23d309d4 from 6.2.y.
I'll test it.
-boris
next prev parent reply other threads:[~2025-09-11 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 0:28 [PATCH v3 5.15.y 0/3] Fix TSA CPUID management in KVM Boris Ostrovsky
2025-09-10 0:28 ` [PATCH v3 5.15.y 1/3] KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code Boris Ostrovsky
2025-09-11 12:33 ` Greg KH
2025-09-11 15:40 ` Boris Ostrovsky [this message]
2025-09-12 21:36 ` Boris Ostrovsky
2025-09-10 0:28 ` [PATCH v3 5.15.y 2/3] KVM: SVM: Return TSA_SQ_NO and TSA_L1_NO bits in __do_cpuid_func() Boris Ostrovsky
2025-09-10 0:28 ` [PATCH v3 5.15.y 3/3] KVM: SVM: Set synthesized TSA CPUID flags Boris Ostrovsky
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=ddbba881-5c51-464f-a41d-2ea39e0183b3@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.