All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: Stefano Stabellini <sstabellini@kernel.org>,
	xen-devel@lists.xenproject.org
Cc: Stefano Stabellini <stefano.stabellini@xilinx.com>,
	andrew.cooper3@citrix.com, george.dunlap@citrix.com,
	iwj@xenproject.org, jbeulich@suse.com, wl@xen.org
Subject: Re: [PATCH v4 1/2] xen: EXPERT clean-up and introduce UNSUPPORTED
Date: Tue, 26 Jan 2021 13:51:01 +0000	[thread overview]
Message-ID: <616b0552-33fc-360e-664c-44178e5afc6a@xen.org> (raw)
In-Reply-To: <20210125212747.26676-1-sstabellini@kernel.org>

Hi Stefano,

On 25/01/2021 21:27, Stefano Stabellini wrote:
>   config ARM_SSBD
> -	bool "Speculative Store Bypass Disable" if EXPERT
> +	bool "Speculative Store Bypass Disable (UNSUPPORTED)" if UNSUPPORTED
>   	depends on HAS_ALTERNATIVE
>   	default y
>   	help
> @@ -87,7 +87,7 @@ config ARM_SSBD
>   	  If unsure, say Y.
>   
>   config HARDEN_BRANCH_PREDICTOR
> -	bool "Harden the branch predictor against aliasing attacks" if EXPERT
> +	bool "Harden the branch predictor against aliasing attacks (UNSUPPORTED)" if UNSUPPORTED
>   	default y
>   	help
>   	  Speculation attacks against some high-performance processors rely on

I read through the back and forth between Bertrand and Jan about 
"UNSUPPORTED". However, I still don't understand why those two options 
are moved to UNSUPPORTED.

Both options will only build the code to enable the mitigation. The 
decision is still based on the processor you are running on.

In addition to that, ARM_SSBD can also be forced enabled/disabled on the 
command line.

A user may want to compile out the code if the target processor is not 
the affected by the two issues. This wouldn't be much different to Xen 
deciding to not enabling the mitigation.

I would view the two options as supported but not security supported. So 
this seems to fit exactly in the definition of EXPERT rather than 
UNSUPPORTED.

Cheers,

-- 
Julien Grall


  parent reply	other threads:[~2021-01-26 13:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-25 21:27 [PATCH v4 0/2] introduce UNSUPPORTED Stefano Stabellini
2021-01-25 21:27 ` [PATCH v4 1/2] xen: EXPERT clean-up and " Stefano Stabellini
2021-01-26  9:22   ` Jan Beulich
2021-01-26 11:06     ` Bertrand Marquis
2021-01-26 11:11       ` Jan Beulich
2021-01-26 11:17         ` Bertrand Marquis
2021-01-26 13:08           ` Jan Beulich
2021-01-26 13:17             ` Ian Jackson
2021-01-26 13:19               ` Jan Beulich
2021-01-26 13:20                 ` Bertrand Marquis
2021-01-26 15:18                   ` Marek Marczykowski-Górecki
2021-01-26 15:23               ` Jan Beulich
2021-01-26 18:28             ` Stefano Stabellini
2021-01-26 13:51   ` Julien Grall [this message]
2021-01-26 14:23     ` Bertrand Marquis
2021-01-26 18:26     ` Stefano Stabellini
2021-01-25 21:27 ` [PATCH v4 2/2] xen: add (EXPERT) to one-line descriptions when appropriate Stefano Stabellini
2021-01-26  9:26   ` Jan Beulich
2021-01-26 18:36     ` Stefano Stabellini
2021-01-26 11:08   ` Bertrand Marquis

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=616b0552-33fc-360e-664c-44178e5afc6a@xen.org \
    --to=julien@xen.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=iwj@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=sstabellini@kernel.org \
    --cc=stefano.stabellini@xilinx.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.