On 2023/8/28 21:58, Igor Mammedov wrote:
On Mon, 28 Aug 2023 16:45:30 +0800
LIU Zhiwei wrote:
Some times we want to know what is the really mean of one cpu option.
For example, in RISC-V, we usually specify a cpu in this way:
-cpu rv64,v=on
If we don't look into the source code, we can't
On 8/28/23 10:58, Igor Mammedov wrote:
On Mon, 28 Aug 2023 16:45:30 +0800
LIU Zhiwei wrote:
Some times we want to know what is the really mean of one cpu option.
For example, in RISC-V, we usually specify a cpu in this way:
-cpu rv64,v=on
If we don't look into the source code, we can't
On Mon, 28 Aug 2023 16:45:30 +0800
LIU Zhiwei wrote:
> Some times we want to know what is the really mean of one cpu option.
> For example, in RISC-V, we usually specify a cpu in this way:
> -cpu rv64,v=on
>
> If we don't look into the source code, we can't get the ISA extensions
> of this -cpu
Some times we want to know what is the really mean of one cpu option.
For example, in RISC-V, we usually specify a cpu in this way:
-cpu rv64,v=on
If we don't look into the source code, we can't get the ISA extensions
of this -cpu command line.
In this patch set, we add one list_cpu_props API
