From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Bertrand Marquis <bertrand.marquis@arm.com>,
<xen-devel@lists.xenproject.org>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Julien Grall <julien@xen.org>,
Volodymyr Babchuk <Volodymyr_Babchuk@epam.com>
Subject: Re: [PATCH] xen/arm: Warn user on cpu errata 832075
Date: Wed, 14 Oct 2020 12:35:15 +0100 [thread overview]
Message-ID: <26742825-25fc-0f82-2b20-d536e8380b2a@citrix.com> (raw)
In-Reply-To: <f11fe960a111530501fd0c20893bec4e32edf3cb.1602671985.git.bertrand.marquis@arm.com>
On 14/10/2020 11:41, Bertrand Marquis wrote:
> When a Cortex A57 processor is affected by CPU errata 832075, a guest
> not implementing the workaround for it could deadlock the system.
> Add a warning during boot informing the user that only trusted guests
> should be executed on the system.
> An equivalent warning is already given to the user by KVM on cores
> affected by this errata.
>
> Signed-off-by: Bertrand Marquis <bertrand.marquis@arm.com>
> ---
> xen/arch/arm/cpuerrata.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/xen/arch/arm/cpuerrata.c b/xen/arch/arm/cpuerrata.c
> index 6c09017515..8f9ab6dde1 100644
> --- a/xen/arch/arm/cpuerrata.c
> +++ b/xen/arch/arm/cpuerrata.c
> @@ -240,6 +240,26 @@ static int enable_ic_inv_hardening(void *data)
>
> #endif
>
> +#ifdef CONFIG_ARM64_ERRATUM_832075
> +
> +static int warn_device_load_acquire_errata(void *data)
> +{
> + static bool warned = false;
> +
> + if ( !warned )
> + {
> + warning_add("This CPU is affected by the errata 832075.\n"
> + "Guests without required CPU erratum workarounds\n"
> + "can deadlock the system!\n"
> + "Only trusted guests should be used on this system.\n");
> + warned = true;
This is an antipattern, which probably wants fixing elsewhere as well.
warning_add() is __init. It's not legitimate to call from a non-init
function, and a less useless build system would have modpost to object.
The ARM_SMCCC_ARCH_WORKAROUND_1 instance asserts based on system state,
but this provides no safety at all.
What warning_add() actually does is queue messages for some point near
the end of boot. It's not clear that this is even a clever thing to do.
I'm very tempted to suggest a blanket change to printk_once().
~Andrew
> + }
> +
> + return 0;
> +}
> +
> +#endif
> +
> #ifdef CONFIG_ARM_SSBD
>
> enum ssbd_state ssbd_state = ARM_SSBD_RUNTIME;
> @@ -419,6 +439,7 @@ static const struct arm_cpu_capabilities arm_errata[] = {
> .capability = ARM64_WORKAROUND_DEVICE_LOAD_ACQUIRE,
> MIDR_RANGE(MIDR_CORTEX_A57, 0x00,
> (1 << MIDR_VARIANT_SHIFT) | 2),
> + .enable = warn_device_load_acquire_errata,
> },
> #endif
> #ifdef CONFIG_ARM64_ERRATUM_834220
next prev parent reply other threads:[~2020-10-14 11:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-14 10:41 [PATCH] xen/arm: Warn user on cpu errata 832075 Bertrand Marquis
2020-10-14 11:11 ` Julien Grall
2020-10-14 16:00 ` Bertrand Marquis
2020-10-14 20:46 ` Stefano Stabellini
2020-10-14 11:35 ` Andrew Cooper [this message]
2020-10-14 16:03 ` Bertrand Marquis
2020-10-14 17:22 ` Julien Grall
2020-10-14 21:15 ` Stefano Stabellini
2020-10-15 10:10 ` Bertrand Marquis
2020-10-15 18:05 ` Stefano Stabellini
2020-10-21 9:03 ` Julien Grall
2020-10-21 9:44 ` Bertrand Marquis
2020-10-21 9:46 ` Julien Grall
2020-10-21 9:52 ` Bertrand Marquis
2020-10-14 17:13 ` Julien Grall
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=26742825-25fc-0f82-2b20-d536e8380b2a@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).