public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: X86 ML <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
	John Allen <john.allen@amd.com>
Subject: Re: [PATCH 1/2] x86/microcode/AMD: Add a patch revision number union
Date: Thu, 21 Mar 2024 20:24:59 +0100	[thread overview]
Message-ID: <ZfyJi2xFbxqyNR/G@gmail.com> (raw)
In-Reply-To: <20240321120548.22687-1-bp@alien8.de>


* Borislav Petkov <bp@alien8.de> wrote:

> From: "Borislav Petkov (AMD)" <bp@alien8.de>
> 
> Add a structure which will be used to split the Zen generation of
> microcode revision numbers into its corresponding elements. This will be
> used to match microcode patches a lot easier and obviate the need for
> a equivalence table.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@alien8.de>
> Cc: John Allen <john.allen@amd.com>
> ---
>  arch/x86/include/asm/microcode.h | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
> 
> diff --git a/arch/x86/include/asm/microcode.h b/arch/x86/include/asm/microcode.h
> index 695e569159c1..c1de0a6aefbc 100644
> --- a/arch/x86/include/asm/microcode.h
> +++ b/arch/x86/include/asm/microcode.h
> @@ -47,6 +47,18 @@ struct microcode_intel {
>  	unsigned int			bits[];
>  };
>  
> +union zen_patch_rev {
> +	struct {
> +		__u32 rev	: 8,
> +		      stepping	: 4,
> +		      model	: 4,
> +		      __resv    : 4,
> +		      ext_model	: 4,
> +		      ext_fam	: 8;
> +	};
> +	__u32 ucode_rev;
> +};

s/__resv/__reserved please?

Had to look twice (ok, I'm lying, had to look 3 times) whether it stood for 
'reserved' or some source of 'revision' / 'reservation' thing.

Thanks,

	Ingo

      parent reply	other threads:[~2024-03-21 19:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21 12:05 [PATCH 1/2] x86/microcode/AMD: Add a patch revision number union Borislav Petkov
2024-03-21 12:05 ` [PATCH 2/2] x86/CPU/AMD: Improve the erratum 1386 workaround Borislav Petkov
2024-03-21 15:21   ` Maciej S. Szmigiero
2024-03-24 20:05     ` [PATCH -v2] " Borislav Petkov
2024-03-25 12:45       ` Maciej S. Szmigiero
2024-03-25 13:01         ` Borislav Petkov
2024-03-25 13:23       ` [tip: x86/cpu] " tip-bot2 for Borislav Petkov (AMD)
2024-03-21 19:26   ` [PATCH 2/2] " Ingo Molnar
2024-03-21 19:24 ` Ingo Molnar [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=ZfyJi2xFbxqyNR/G@gmail.com \
    --to=mingo@kernel.org \
    --cc=bp@alien8.de \
    --cc=john.allen@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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