From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 1/4] x86/spec: print the built-in SPECULATIVE_HARDEN_* options
Date: Tue, 27 Feb 2024 12:13:09 +0100 [thread overview]
Message-ID: <Zd3DxW88JoyUSU4m@macbook> (raw)
In-Reply-To: <85fa5e55-27c5-495d-bd7b-857260b1de20@suse.com>
On Mon, Feb 26, 2024 at 01:39:49PM +0100, Jan Beulich wrote:
> On 26.02.2024 12:07, Roger Pau Monne wrote:
> > Just like it's done for INDIRECT_THUNK and SHADOW_PAGING.
> >
> > Reported-by: Jan Beulich <jbeulich@suse.com>
> > Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
>
> In principle
> Reviewed-by: Jan Beulich <jbeulich@suse.com>
> but ...
>
> > --- a/xen/arch/x86/spec_ctrl.c
> > +++ b/xen/arch/x86/spec_ctrl.c
> > @@ -466,13 +466,25 @@ static void __init print_details(enum ind_thunk thunk)
> > (e21a & cpufeat_mask(X86_FEATURE_SBPB)) ? " SBPB" : "");
> >
> > /* Compiled-in support which pertains to mitigations. */
> > - if ( IS_ENABLED(CONFIG_INDIRECT_THUNK) || IS_ENABLED(CONFIG_SHADOW_PAGING) )
> > + if ( IS_ENABLED(CONFIG_INDIRECT_THUNK) || IS_ENABLED(CONFIG_SHADOW_PAGING) ||
> > + IS_ENABLED(CONFIG_SPECULATIVE_HARDEN_ARRAY) ||
> > + IS_ENABLED(CONFIG_SPECULATIVE_HARDEN_BRANCH) ||
> > + IS_ENABLED(CONFIG_SPECULATIVE_HARDEN_GUEST_ACCESS) )
> > printk(" Compiled-in support:"
> > #ifdef CONFIG_INDIRECT_THUNK
> > " INDIRECT_THUNK"
> > #endif
> > #ifdef CONFIG_SHADOW_PAGING
> > " SHADOW_PAGING"
> > +#endif
> > +#ifdef CONFIG_SPECULATIVE_HARDEN_ARRAY
> > + " SPECULATIVE_HARDEN_ARRAY"
> > +#endif
> > +#ifdef CONFIG_SPECULATIVE_HARDEN_BRANCH
> > + " SPECULATIVE_HARDEN_BRANCH"
> > +#endif
> > +#ifdef CONFIG_SPECULATIVE_HARDEN_GUEST_ACCESS
> > + " SPECULATIVE_HARDEN_GUEST_ACCESS"
> > #endif
>
> ... I'd like to suggest to drop the SPECULATIVE_ from the string literals.
> They're relevant in the Kconfig identifiers, but they're imo redundant in
> the context of these log messages. (Happy to adjust while committing, if
> need be.)
Oh, yes, indeed, we already print HARDEN_BRANCH instead of
SPECULATIVE_HARDEN_BRANCH. Please adjust at commit if you don't mind.
Thanks, Roger.
next prev parent reply other threads:[~2024-02-27 11:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 11:07 [PATCH v3 0/4] x86/spec: improve command line parsing Roger Pau Monne
2024-02-26 11:07 ` [PATCH v3 1/4] x86/spec: print the built-in SPECULATIVE_HARDEN_* options Roger Pau Monne
2024-02-26 12:39 ` Jan Beulich
2024-02-27 11:13 ` Roger Pau Monné [this message]
2024-02-26 11:07 ` [PATCH v3 2/4] x86/spec: fix BRANCH_HARDEN option to only be set when build-enabled Roger Pau Monne
2024-02-26 12:42 ` Jan Beulich
2024-02-26 11:07 ` [PATCH v3 3/4] x86/spec: fix INDIRECT_THUNK " Roger Pau Monne
2024-02-26 12:50 ` Jan Beulich
2024-02-27 11:18 ` Roger Pau Monné
2024-02-26 11:07 ` [PATCH v3 4/4] x86/spec: do not print thunk option selection if not built-in Roger Pau Monne
2024-02-26 12:54 ` Jan Beulich
2024-02-27 11:20 ` Roger Pau Monné
2024-02-27 13:23 ` Jan Beulich
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=Zd3DxW88JoyUSU4m@macbook \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.