From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>, Wei Liu <wl@xen.org>,
Alejandro Vallejo <alejandro.vallejo@cloud.com>,
Stefano Stabellini <stefano.stabellini@amd.com>,
Xenia Ragiadakou <xenia.ragiadakou@amd.com>
Subject: Re: [PATCH v2 2/2] x86/Kconfig: Introduce CONFIG_{AMD,INTEL} and conditionalise ucode
Date: Wed, 10 Apr 2024 18:34:13 +0200 [thread overview]
Message-ID: <Zha_hXU3zRwVzFZN@macbook> (raw)
In-Reply-To: <2fd969ef-8326-4ae8-a568-4256f00542f0@citrix.com>
On Wed, Apr 10, 2024 at 05:21:37PM +0100, Andrew Cooper wrote:
> On 10/04/2024 4:14 pm, Roger Pau Monné wrote:
> > On Thu, Oct 26, 2023 at 09:55:39PM +0100, Andrew Cooper wrote:
> >> +
> >> +config AMD
> >> + bool "AMD"
> >> + default y
> >> + help
> >> + Detection, tunings and quirks for AMD platforms.
> >> +
> >> + May be turned off in builds targetting other vendors. Otherwise,
> >> + must be enabled for Xen to work suitably on AMD platforms.
> >> +
> >> +config INTEL
> >> + bool "Intel"
> >> + default y
> >> + help
> >> + Detection, tunings and quirks for Intel platforms.
> >> +
> >> + May be turned off in builds targetting other vendors. Otherwise,
> >> + must be enabled for Xen to work suitably on Intel platforms.
> > There seems to be a weird mix between hard tabs and spaces above.
> > Naming is OK for me.
>
> Yeah. I already fixed those locally.
With that fixed:
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
> >> +
> >> +endmenu
> >> diff --git a/xen/arch/x86/cpu/microcode/Makefile b/xen/arch/x86/cpu/microcode/Makefile
> >> index aae235245b06..30d600544f45 100644
> >> --- a/xen/arch/x86/cpu/microcode/Makefile
> >> +++ b/xen/arch/x86/cpu/microcode/Makefile
> >> @@ -1,3 +1,3 @@
> >> -obj-y += amd.o
> >> +obj-$(CONFIG_AMD) += amd.o
> >> obj-y += core.o
> >> -obj-y += intel.o
> >> +obj-$(CONFIG_INTEL) += intel.o
> >> diff --git a/xen/arch/x86/cpu/microcode/private.h b/xen/arch/x86/cpu/microcode/private.h
> >> index b58611e908aa..da556fe5060a 100644
> >> --- a/xen/arch/x86/cpu/microcode/private.h
> >> +++ b/xen/arch/x86/cpu/microcode/private.h
> >> @@ -70,7 +70,16 @@ struct microcode_ops {
> >> * support available) and (not) ops->apply_microcode (i.e. read only).
> >> * Otherwise, all hooks must be filled in.
> >> */
> >> +#ifdef CONFIG_AMD
> >> void ucode_probe_amd(struct microcode_ops *ops);
> >> +#else
> >> +static inline void ucode_probe_amd(struct microcode_ops *ops) {}
> >> +#endif
> >> +
> >> +#ifdef CONFIG_INTEL
> >> void ucode_probe_intel(struct microcode_ops *ops);
> >> +#else
> >> +static inline void ucode_probe_intel(struct microcode_ops *ops) {}
> > This is stale now, and will need some updating to match what's in
> > private.h.
>
> There's nothing state I can see.
>
> Patch 1 does significantly edit this vs what's currently in staging.
Oh, sorry, I'm missed patch 1 then.
Thanks, Roger.
next prev parent reply other threads:[~2024-04-10 16:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-26 20:55 [PATCH v2 0/2] x86: ucode and CPU Kconfig Andrew Cooper
2023-10-26 20:55 ` [PATCH v2 1/2] x86/ucode: Move vendor specifics back out of early_microcode_init() Andrew Cooper
2023-10-26 20:55 ` [PATCH v2 2/2] x86/Kconfig: Introduce CONFIG_{AMD,INTEL} and conditionalise ucode Andrew Cooper
2023-10-27 7:12 ` Jan Beulich
[not found] ` <ZTu_WxdWTrthCs4m@macbook>
2023-10-27 19:18 ` Andrew Cooper
2023-10-30 8:40 ` Jan Beulich
2023-10-30 9:07 ` Roger Pau Monné
2023-10-27 19:19 ` [PATCH v2.5 " Andrew Cooper
2024-04-09 21:42 ` Stefano Stabellini
2024-04-09 21:49 ` Andrew Cooper
2024-04-10 15:14 ` [PATCH v2 " Roger Pau Monné
2024-04-10 16:21 ` Andrew Cooper
2024-04-10 16:34 ` Roger Pau Monné [this message]
2024-04-10 17:49 ` Andrew Cooper
2024-04-10 18:18 ` Stefano Stabellini
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=Zha_hXU3zRwVzFZN@macbook \
--to=roger.pau@citrix.com \
--cc=JBeulich@suse.com \
--cc=alejandro.vallejo@cloud.com \
--cc=andrew.cooper3@citrix.com \
--cc=stefano.stabellini@amd.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xenia.ragiadakou@amd.com \
/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.