From: Leif Lindholm <leif@nuviainc.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org,
"Radosław Biernacki" <rad@semihalf.com>
Subject: Re: [PATCH 2/2] sbsa-ref: add 'max' to list of allowed cpus
Date: Thu, 11 Feb 2021 14:16:09 +0000 [thread overview]
Message-ID: <20210211141609.GZ1664@vanye> (raw)
In-Reply-To: <20210211123638.1820482-2-marcin.juszkiewicz@linaro.org>
On Thu, Feb 11, 2021 at 13:36:38 +0100, Marcin Juszkiewicz wrote:
> Let add 'max' cpu while work goes on adding newer CPU types than
> Cortex-A72. This allows us to check SVE etc support.
>
> Signed-off-by: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Acked-by: Leif Lindholm <leif@nuviainc.com>
> ---
> hw/arm/sbsa-ref.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git hw/arm/sbsa-ref.c hw/arm/sbsa-ref.c
> index 276243d122..88dfb2284c 100644
> --- hw/arm/sbsa-ref.c
> +++ hw/arm/sbsa-ref.c
> @@ -147,6 +147,7 @@ static const int sbsa_ref_irqmap[] = {
> static const char * const valid_cpus[] = {
> ARM_CPU_TYPE_NAME("cortex-a57"),
> ARM_CPU_TYPE_NAME("cortex-a72"),
> + ARM_CPU_TYPE_NAME("max"),
> };
>
> static bool cpu_type_valid(const char *cpu)
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-02-11 14:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 12:20 [PATCH] sbsa-ref: remove cortex-a53 from list of supported cpus Marcin Juszkiewicz
2021-02-11 12:24 ` no-reply
2021-02-11 12:36 ` [PATCH 1/2] " Marcin Juszkiewicz
2021-02-11 12:36 ` [PATCH 2/2] sbsa-ref: add 'max' to list of allowed cpus Marcin Juszkiewicz
2021-02-11 14:16 ` Leif Lindholm [this message]
2021-02-11 13:44 ` [PATCH 1/2] sbsa-ref: remove cortex-a53 from list of supported cpus Philippe Mathieu-Daudé
2021-02-11 14:16 ` Leif Lindholm
2021-02-16 14:23 ` Peter Maydell
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=20210211141609.GZ1664@vanye \
--to=leif@nuviainc.com \
--cc=marcin.juszkiewicz@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rad@semihalf.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 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).