Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: stable@vger.kernel.org, sashal@kernel.org, bp@alien8.de
Subject: Re: [PATCH 5.15.y 2/2] KVM: SVM: Properly advertise TSA CPUID bits to guests
Date: Thu, 4 Sep 2025 13:59:14 +0200	[thread overview]
Message-ID: <2025090443-pull-anchovy-1b65@gregkh> (raw)
In-Reply-To: <dddfe42e-31c1-4bf8-b15b-b7585b708a04@oracle.com>

On Wed, Sep 03, 2025 at 12:44:00PM -0400, Boris Ostrovsky wrote:
> 
> 
> On 9/2/25 7:42 AM, Greg KH wrote:
> > On Wed, Aug 27, 2025 at 02:15:24PM -0400, Boris Ostrovsky wrote:
> > > Commit 31272abd5974b38ba312e9cf2ec2f09f9dd7dcba upstream.
> > > Commit f3f9deccfc68a6b7c8c1cc51e902edba23d309d4 LTS
> > 
> > How about you just backport both of these independently, as this change
> > now looks nothing like either of those commits :(
> 
> The trouble is that the first one was already backported by
> c334ae4a545a1b1ae8aff4e5eb741af2c7624cc7 and it missed a few things. Some,
> but not all, of these issues were corrected by the LTS patch (the second
> commit above).
> 
> I couldn't figure out how to separate this into two patches so I merged them
> into one.
> 
> I suppose I could provide an incomplete "fix" for
> c334ae4a545a1b1ae8aff4e5eb741af2c7624cc7 as a separate patch (but the code
> will still be broken) and then do the LTS backport.

Yes please.  When ever possible try to stick to what is upstream, and
that includes backporting partial patches if needed, as then they can
actually be tracked.

thanks,

greg k-h

      reply	other threads:[~2025-09-04 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27 18:15 [PATCH 5.15.y 0/2] Fix TSA CPUID management in KVM Boris Ostrovsky
2025-08-27 18:15 ` [PATCH 5.15.y 1/2] KVM: x86: Move open-coded CPUID leaf 0x80000021 EAX bit propagation code Boris Ostrovsky
2025-08-27 18:15 ` [PATCH 5.15.y 2/2] KVM: SVM: Properly advertise TSA CPUID bits to guests Boris Ostrovsky
2025-09-02 11:42   ` Greg KH
2025-09-03 16:44     ` Boris Ostrovsky
2025-09-04 11:59       ` Greg KH [this message]

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=2025090443-pull-anchovy-1b65@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox