[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2] target/riscv: Don't expose the CPU properties on names CP
From: |
Alistair Francis |
Subject: |
Re: [PATCH v2] target/riscv: Don't expose the CPU properties on names CPUs |
Date: |
Wed, 8 Jun 2022 08:10:07 +1000 |
On Wed, Jun 1, 2022 at 11:37 AM Alistair Francis
<alistair.francis@opensource.wdc.com> wrote:
>
> From: Alistair Francis <alistair.francis@wdc.com>
>
> There are currently two types of RISC-V CPUs:
> - Generic CPUs (base or any) that allow complete custimisation
> - "Named" CPUs that match existing hardware
>
> Users can use the base CPUs to custimise the extensions that they want, for
> example -cpu rv64,v=true.
>
> We originally exposed these as part of the named CPUs as well, but that was
> by accident.
>
> Exposing the CPU properties to named CPUs means that we accidently
> enable extensinos that don't exist on the CPUs by default. For example
> the SiFive E CPU currently support the zba extension, which is a bug.
>
> This patch instead only expose the CPU extensions to the generic CPUs.
>
> Signed-off-by: Alistair Francis <alistair.francis@wdc.com>
Any thoughts?
Alistair
- Re: [PATCH v2] target/riscv: Don't expose the CPU properties on names CPUs,
Alistair Francis <=