From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: Gavin Shan <gshan@redhat.com>,
qemu-devel@nongnu.org, David Hildenbrand <david@redhat.com>
Cc: "Chris Wulff" <crwulff@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
qemu-s390x@nongnu.org, "Weiwei Li" <liweiwei@iscas.ac.cn>,
qemu-arm@nongnu.org,
"Mark Cave-Ayland" <mark.cave-ayland@ilande.co.uk>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Yoshinori Sato" <ysato@users.sourceforge.jp>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Max Filippov" <jcmvbkbc@gmail.com>,
"Nicholas Piggin" <npiggin@gmail.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Ilya Leoshkevich" <iii@linux.ibm.com>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>,
"Greg Kurz" <groug@kaod.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
qemu-ppc@nongnu.org,
"Daniel Henrique Barboza" <dbarboza@ventanamicro.com>,
"Marek Vasut" <marex@denx.de>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Michael Rolnik" <mrolnik@gmail.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-riscv@nongnu.org, "Aurelien Jarno" <aurelien@aurel32.net>,
"Bin Meng" <bin.meng@windriver.com>,
"Xiaojuan Yang" <yangxiaojuan@loongson.cn>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Artyom Tarasenko" <atar4qemu@gmail.com>,
"Song Gao" <gaosong@loongson.cn>,
"Stafford Horne" <shorne@gmail.com>,
"Yanan Wang" <wangyanan55@huawei.com>,
"Alistair Francis" <alistair.francis@wdc.com>,
"Brian Cain" <bcain@quicinc.com>,
"Cédric Le Goater" <clg@kaod.org>,
"Thomas Huth" <thuth@redhat.com>,
"Liu Zhiwei" <zhiwei_liu@linux.alibaba.com>
Subject: Re: [PATCH 3/4] hw/cpu: Introduce CPUClass::cpu_resolving_type field
Date: Mon, 11 Sep 2023 11:43:00 +0200 [thread overview]
Message-ID: <af78b6c9-14e5-3256-9670-c106f4942140@linaro.org> (raw)
In-Reply-To: <87cb0174-c652-aa44-be7c-49e78e0a5003@redhat.com>
On 11/9/23 01:28, Gavin Shan wrote:
> Hi Philippe,
>
> On 9/8/23 21:22, Philippe Mathieu-Daudé wrote:
>> Add a field to return the QOM type name of a CPU class.
>>
>> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> ---
>> include/hw/core/cpu.h | 2 ++
>> hw/core/cpu-common.c | 2 +-
>> target/alpha/cpu.c | 1 +
>> target/arm/cpu.c | 1 +
>> target/avr/cpu.c | 1 +
>> target/cris/cpu.c | 1 +
>> target/hexagon/cpu.c | 1 +
>> target/hppa/cpu.c | 1 +
>> target/i386/cpu.c | 1 +
>> target/loongarch/cpu.c | 1 +
>> target/m68k/cpu.c | 1 +
>> target/microblaze/cpu.c | 1 +
>> target/mips/cpu.c | 1 +
>> target/nios2/cpu.c | 1 +
>> target/openrisc/cpu.c | 1 +
>> target/ppc/cpu_init.c | 1 +
>> target/riscv/cpu.c | 1 +
>> target/rx/cpu.c | 1 +
>> target/s390x/cpu.c | 1 +
>> target/sh4/cpu.c | 1 +
>> target/sparc/cpu.c | 1 +
>> target/tricore/cpu.c | 1 +
>> target/xtensa/cpu.c | 1 +
>> 23 files changed, 24 insertions(+), 1 deletion(-)
>>
>> diff --git a/include/hw/core/cpu.h b/include/hw/core/cpu.h
>> index 129d179937..e469efd409 100644
>> --- a/include/hw/core/cpu.h
>> +++ b/include/hw/core/cpu.h
>> @@ -100,6 +100,7 @@ struct SysemuCPUOps;
>> /**
>> * CPUClass:
>> + * @cpu_resolving_type: CPU QOM type name
>> * @class_by_name: Callback to map -cpu command line model name to an
>> * instantiatable CPU type.
>> * @parse_features: Callback to parse command line arguments.
>> @@ -148,6 +149,7 @@ struct CPUClass {
>> DeviceClass parent_class;
>> /*< public >*/
>> + const char *cpu_resolving_type;
>> ObjectClass *(*class_by_name)(const char *cpu_model);
>> void (*parse_features)(const char *typename, char *str, Error
>> **errp);
>
> The question is why not use CPU_RESOLVING_TYPE directly? It seems
> CPU_RESOLVING_TYPE
> is exactly what you want here.
Unfortunately CPU_RESOLVING_TYPE is target-specific, we want
hw/core/cpu-common.c to be target-agnostic (build once for all
targets). This is particularly important in the context of
heterogeneous QEMU, where a single binary will be able to create
CPUs from different targets.
> Besides, I guess the changes can be
> squeezed into two
> patches (commits) as below:
>
> PATCH[1] target/alpha: Tidy up alpha_cpu_class_by_name()
> PATCH[2] Move the checks (oc == NULL || object_class_is_abstract() ||
> !object_class_dynamic_cast())
> from individual targets to
> hw/core/cpu-common.c::cpu_class_by_name()
>
> I rebase my series of '[PATCH v3 00/32] Unified CPU type check' on top
> of yours. Please
> let me know if I need to include your patch into my v4 series for
> review. In that case,
> I can include your patches with above changes applied.
>
> Thanks,
> Gavin
>
>> diff --git a/hw/core/cpu-common.c b/hw/core/cpu-common.c
>> index c6a0c9390c..2d24261a6a 100644
>> --- a/hw/core/cpu-common.c
>> +++ b/hw/core/cpu-common.c
>> @@ -155,7 +155,7 @@ ObjectClass *cpu_class_by_name(const char
>> *typename, const char *cpu_model)
>> assert(cpu_model);
>> oc = object_class_by_name(typename);
>> cc = CPU_CLASS(oc);
>> - assert(cc->class_by_name);
>> + assert(cc->cpu_resolving_type && cc->class_by_name);
>> oc = cc->class_by_name(cpu_model);
>> if (oc == NULL || object_class_is_abstract(oc)) {
>> return NULL;
next prev parent reply other threads:[~2023-09-11 9:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 11:22 [PATCH 0/4] hw/core/cpu-common: Consolidate cpu_class_by_name() Philippe Mathieu-Daudé
2023-09-08 11:22 ` [PATCH 1/4] target/alpha: Tidy up alpha_cpu_class_by_name() Philippe Mathieu-Daudé
2023-09-09 22:17 ` Richard Henderson
2023-09-10 23:29 ` Gavin Shan
2023-09-08 11:22 ` [PATCH 2/4] hw/cpu: Call object_class_is_abstract() once in cpu_class_by_name() Philippe Mathieu-Daudé
2023-09-09 22:18 ` Richard Henderson
2023-09-08 11:22 ` [PATCH 3/4] hw/cpu: Introduce CPUClass::cpu_resolving_type field Philippe Mathieu-Daudé
2023-09-09 22:21 ` Richard Henderson
2023-09-10 23:28 ` Gavin Shan
2023-09-11 9:43 ` Philippe Mathieu-Daudé [this message]
2023-09-11 10:55 ` Igor Mammedov
2023-09-11 22:40 ` Gavin Shan
2023-09-25 0:24 ` Gavin Shan
2023-10-11 3:28 ` Philippe Mathieu-Daudé
2023-10-11 6:45 ` Gavin Shan
2023-09-08 11:22 ` [PATCH 4/4] hw/cpu: Call object_class_dynamic_cast() once in cpu_class_by_name() Philippe Mathieu-Daudé
2023-09-09 23:26 ` Richard Henderson
2023-09-10 23:40 ` Gavin Shan
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=af78b6c9-14e5-3256-9670-c106f4942140@linaro.org \
--to=philmd@linaro.org \
--cc=aleksandar.rikalo@syrmia.com \
--cc=alistair.francis@wdc.com \
--cc=atar4qemu@gmail.com \
--cc=aurelien@aurel32.net \
--cc=bcain@quicinc.com \
--cc=bin.meng@windriver.com \
--cc=clg@kaod.org \
--cc=crwulff@gmail.com \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=david@redhat.com \
--cc=dbarboza@ventanamicro.com \
--cc=edgar.iglesias@gmail.com \
--cc=eduardo@habkost.net \
--cc=gaosong@loongson.cn \
--cc=groug@kaod.org \
--cc=gshan@redhat.com \
--cc=iii@linux.ibm.com \
--cc=jcmvbkbc@gmail.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=laurent@vivier.eu \
--cc=liweiwei@iscas.ac.cn \
--cc=marcel.apfelbaum@gmail.com \
--cc=marex@denx.de \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=mrolnik@gmail.com \
--cc=npiggin@gmail.com \
--cc=palmer@dabbelt.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-riscv@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shorne@gmail.com \
--cc=thuth@redhat.com \
--cc=wangyanan55@huawei.com \
--cc=yangxiaojuan@loongson.cn \
--cc=ysato@users.sourceforge.jp \
--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).