All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Borislav Petkov (AMD)" <bp@alien8.de>, stable@vger.kernel.org
Subject: Re: Request to port to 6.6.y : c809b0d0e52d ("x86/microcode/AMD: Flush patch buffer mapping after application")
Date: Mon, 23 Dec 2024 14:23:48 +0100	[thread overview]
Message-ID: <Z2lkZC_MgXe4rDRW@antipodes> (raw)
In-Reply-To: <2024122345-demotion-zit-15c6@gregkh>

On Mon, Dec 23, 2024 at 01:33:17PM +0100, Greg KH wrote:
> Wait, why do you want these for the 6.6.y tree if you haven't even
> tested to see if they are required or work there?  Why not just move to
> 6.12.y instead as you know that works.

The original problem was reported by me on 6.6.y.
I tested the patch provided by Borislav on 6.6.y. As mentioned, a small change
is required to make it compile, but this is a nonfunctional change in the
tested code path and so didn't influence test results.
I can therefore say with certainty that the fix is required on 6.6.y .

In these discussions, I requested Borislav if the patch could also be submitted
for 6.6.y, and made him aware that variable 'bsp_cpuid_1_eax' used in the patch
does not yet exist in that branch. He replied [1]:

    "That's fine - stable folks usually know what to pick up. If not, I'll
    provide backports."


I cannot currently move to 6.12 for these systems, this has other consequences
and testing efforts.

Thanks,
Thomas

[1] https://lore.kernel.org/lkml/20241119111728.GAZzxzyHj8U99cEHQ8@fat_crate.local/

  reply	other threads:[~2024-12-23 13:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17 15:32 Request to port to 6.6.y : c809b0d0e52d ("x86/microcode/AMD: Flush patch buffer mapping after application") Thomas De Schampheleire
2024-12-17 15:53 ` Greg KH
2024-12-18 12:28   ` Thomas De Schampheleire
2024-12-23 12:33     ` Greg KH
2024-12-23 13:23       ` Thomas De Schampheleire [this message]
2024-12-23 15:49         ` Greg KH

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=Z2lkZC_MgXe4rDRW@antipodes \
    --to=thomas.de_schampheleire@nokia.com \
    --cc=bp@alien8.de \
    --cc=gregkh@linuxfoundation.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.