From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: Bin Meng <bmeng.cn@gmail.com>,
devel@lists.libvirt.org, Weiwei Li <liwei1518@gmail.com>,
qemu-riscv@nongnu.org,
Daniel Henrique Barboza <dbarboza@ventanamicro.com>,
Liu Zhiwei <zhiwei_liu@linux.alibaba.com>,
Alistair Francis <alistair.francis@wdc.com>,
Palmer Dabbelt <palmer@dabbelt.com>
Subject: Re: [PATCH-for-9.1] target/riscv: Remove the deprecated 'any' CPU type
Date: Thu, 25 Jul 2024 09:03:55 +0200 [thread overview]
Message-ID: <2eb95ab8-a89f-47d5-8fdf-e6eabefb0781@linaro.org> (raw)
In-Reply-To: <20240724130717.95629-1-philmd@linaro.org>
On 24/7/24 15:07, Philippe Mathieu-Daudé wrote:
> The 'any' CPU is deprecated since commit f57d5f8004b
> ("target/riscv: deprecate the 'any' CPU type"). Users
> are better off using the default CPUs or the 'max' CPU.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> docs/about/deprecated.rst | 13 -------------
> docs/about/removed-features.rst | 8 ++++++++
> target/riscv/cpu-qom.h | 1 -
> target/riscv/cpu.c | 28 ----------------------------
> 4 files changed, 8 insertions(+), 42 deletions(-)
>
> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
> index 88f0f037865..0ac49b15b44 100644
> --- a/docs/about/deprecated.rst
> +++ b/docs/about/deprecated.rst
> @@ -347,19 +347,6 @@ QEMU's ``vhost`` feature, which would eliminate the high latency costs under
> which the 9p ``proxy`` backend currently suffers. However as of to date nobody
> has indicated plans for such kind of reimplementation unfortunately.
>
> -RISC-V 'any' CPU type ``-cpu any`` (since 8.2)
> -^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> -
> -The 'any' CPU type was introduced back in 2018 and has been around since the
> -initial RISC-V QEMU port. Its usage has always been unclear: users don't know
> -what to expect from a CPU called 'any', and in fact the CPU does not do anything
> -special that isn't already done by the default CPUs rv32/rv64.
> -
> -After the introduction of the 'max' CPU type, RISC-V now has a good coverage
> -of generic CPUs: rv32 and rv64 as default CPUs and 'max' as a feature complete
> -CPU for both 32 and 64 bit builds. Users are then discouraged to use the 'any'
> -CPU type starting in 8.2.
> -
> RISC-V CPU properties which start with capital 'Z' (since 8.2)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> diff --git a/docs/about/removed-features.rst b/docs/about/removed-features.rst
> index fc7b28e6373..f3e9474a73e 100644
> --- a/docs/about/removed-features.rst
> +++ b/docs/about/removed-features.rst
> @@ -850,6 +850,14 @@ The RISC-V no MMU cpus have been removed. The two CPUs: ``rv32imacu-nommu`` and
> ``rv64imacu-nommu`` can no longer be used. Instead the MMU status can be specified
> via the CPU ``mmu`` option when using the ``rv32`` or ``rv64`` CPUs.
>
> +RISC-V 'any' CPU type ``-cpu any`` (removed in 9.1)
> +'''''''''''''''''''''''''''''''''''''''''''''''''''
My bad, this will be 9.2.
> +
> +The 'any' CPU type was introduced back in 2018 and was around since the
> +initial RISC-V QEMU port. Its usage was always been unclear: users don't know
> +what to expect from a CPU called 'any', and in fact the CPU does not do anything
> +special that isn't already done by the default CPUs rv32/rv64.
next prev parent reply other threads:[~2024-07-25 7:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 13:07 [PATCH-for-9.1] target/riscv: Remove the deprecated 'any' CPU type Philippe Mathieu-Daudé
2024-07-25 7:03 ` Philippe Mathieu-Daudé [this message]
2024-07-25 11:41 ` Daniel Henrique Barboza
2024-07-26 3:51 ` Alistair Francis
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=2eb95ab8-a89f-47d5-8fdf-e6eabefb0781@linaro.org \
--to=philmd@linaro.org \
--cc=alistair.francis@wdc.com \
--cc=bmeng.cn@gmail.com \
--cc=dbarboza@ventanamicro.com \
--cc=devel@lists.libvirt.org \
--cc=liwei1518@gmail.com \
--cc=palmer@dabbelt.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=zhiwei_liu@linux.alibaba.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).