From: Paolo Bonzini <pbonzini@redhat.com>
To: Claudio Fontana <cfontana@suse.de>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Paul Durrant" <paul@xen.org>,
"Cameron Esfahani" <dirty@apple.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Jason Wang" <jasowang@redhat.com>,
"Marcelo Tosatti" <mtosatti@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Peter Xu" <peterx@redhat.com>,
"Bruce Rogers" <brogers@suse.com>,
"Roman Bolshakov" <r.bolshakov@yadro.com>,
"Emilio G . Cota" <cota@braap.org>,
haxm-team@intel.com, "Colin Xu" <colin.xu@intel.com>,
"Anthony Perard" <anthony.perard@citrix.com>,
"Sunil Muthuswamy" <sunilmut@microsoft.com>,
"Dario Faggioli" <dfaggioli@suse.com>,
"Olaf Hering" <ohering@suse.de>,
"Wenchao Wang" <wenchao.wang@intel.com>
Subject: Re: [RFC v5 11/12] i386: centralize initialization of cpu accel interfaces
Date: Thu, 26 Nov 2020 16:14:56 +0100 [thread overview]
Message-ID: <772a0f85-555a-50ee-2b5e-35ff748a589b@redhat.com> (raw)
In-Reply-To: <16445790-3371-9775-3d03-f8c8f0d66b18@suse.de>
On 26/11/20 15:55, Claudio Fontana wrote:
> If we agree to use "accel-cpu" I would lookup "kvm-accel-cpu"
> if we agree to use "accel-x86_64" aka "accel-" CPU_RESOLVING_TYPE, I would lookup "kvm-accel-" CPU_RESOLVING_TYPE
>
> * initialize the arch-specific accel CpuClass interfaces */
> static void accel_init_cpu_interfaces(AccelClass *ac, const char *cpu_type)
> {
> const char *ac_name; /* AccelClass name */
> char *acc_name; /* AccelCPUClass name */
> ObjectClass *acc; /* AccelCPUClass */
>
> ac_name = object_class_get_name(OBJECT_CLASS(ac));
> g_assert(ac_name != NULL);
>
> acc_name = g_strdup_printf("%s-cpu", ac_name);
> acc = object_class_by_name(acc_name);
> g_free(acc_name);
>
> if (acc) {
> object_class_foreach(accel_init_cpu_interfaces_aux, cpu_type, false, acc);
> }
> }
I would use the second; there's no reason to have allow only one CPU
type, it's just a limitation of QEMU.
Paolo
next prev parent reply other threads:[~2020-11-26 15:16 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 16:21 [RFC v5 00/12] i386 cleanup Claudio Fontana
2020-11-24 16:21 ` [RFC v5 01/12] i386: move kvm accel files into kvm/ Claudio Fontana
2020-11-24 16:22 ` [RFC v5 02/12] i386: move whpx accel files into whpx/ Claudio Fontana
2020-11-24 16:22 ` [RFC v5 03/12] i386: move hax accel files into hax/ Claudio Fontana
2020-11-24 16:22 ` [RFC v5 04/12] i386: hvf: remove stale MAINTAINERS entry for old hvf stubs Claudio Fontana
2020-11-24 16:22 ` [RFC v5 05/12] i386: move TCG accel files into tcg/ Claudio Fontana
2020-11-24 16:22 ` [RFC v5 06/12] i386: move cpu dump out of helper.c into cpu-dump.c Claudio Fontana
2020-11-24 16:22 ` [RFC v5 07/12] i386: move TCG cpu class initialization out of helper.c Claudio Fontana
2020-11-24 16:22 ` [RFC v5 08/12] accel: extend AccelState and AccelClass to user-mode Claudio Fontana
2020-11-24 17:56 ` Eduardo Habkost
2020-11-24 18:16 ` Claudio Fontana
2020-11-24 16:22 ` [RFC v5 09/12] module: introduce MODULE_INIT_ACCEL_CPU Claudio Fontana
2020-11-24 17:08 ` Eduardo Habkost
2020-11-24 18:29 ` Claudio Fontana
2020-11-24 19:08 ` Eduardo Habkost
2020-11-24 20:01 ` Paolo Bonzini
2020-11-25 9:21 ` Claudio Fontana
2020-11-25 9:30 ` Paolo Bonzini
2020-11-25 10:42 ` Claudio Fontana
2020-11-26 12:45 ` Claudio Fontana
2020-11-26 11:25 ` Philippe Mathieu-Daudé
2020-11-26 12:03 ` Claudio Fontana
2020-11-24 16:22 ` [RFC v5 10/12] i386: split cpu accelerators from cpu.c Claudio Fontana
2020-11-24 16:22 ` [RFC v5 11/12] i386: centralize initialization of cpu accel interfaces Claudio Fontana
2020-11-24 16:59 ` Eduardo Habkost
2020-11-24 18:38 ` Claudio Fontana
2020-11-24 20:13 ` Paolo Bonzini
2020-11-24 21:31 ` Eduardo Habkost
2020-11-25 9:26 ` Claudio Fontana
2020-11-26 10:57 ` Claudio Fontana
2020-11-26 13:44 ` Eduardo Habkost
2020-11-26 14:33 ` Claudio Fontana
2020-11-26 14:49 ` Eduardo Habkost
2020-11-26 14:55 ` Claudio Fontana
2020-11-26 15:14 ` Eduardo Habkost
2020-11-26 15:34 ` Claudio Fontana
2020-11-26 15:48 ` Eduardo Habkost
2020-11-26 15:49 ` Claudio Fontana
2020-11-26 15:14 ` Paolo Bonzini [this message]
2020-11-25 9:24 ` Claudio Fontana
2020-11-26 14:42 ` Claudio Fontana
2020-11-24 16:22 ` [RFC v5 12/12] accel: centralize initialization of CpusAccelOps Claudio Fontana
2020-11-24 17:48 ` Eduardo Habkost
2020-11-24 18:52 ` Claudio Fontana
2020-11-24 19:27 ` Eduardo Habkost
2020-11-24 19:39 ` Claudio Fontana
2020-11-24 20:34 ` Eduardo Habkost
2020-11-25 9:32 ` Claudio Fontana
2020-11-25 11:48 ` Claudio Fontana
2020-11-25 14:51 ` Eduardo Habkost
2020-11-24 20:14 ` [RFC v5 00/12] i386 cleanup Paolo Bonzini
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=772a0f85-555a-50ee-2b5e-35ff748a589b@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=brogers@suse.com \
--cc=cfontana@suse.de \
--cc=colin.xu@intel.com \
--cc=cota@braap.org \
--cc=dfaggioli@suse.com \
--cc=dirty@apple.com \
--cc=ehabkost@redhat.com \
--cc=haxm-team@intel.com \
--cc=jasowang@redhat.com \
--cc=lvivier@redhat.com \
--cc=mtosatti@redhat.com \
--cc=ohering@suse.de \
--cc=paul@xen.org \
--cc=peterx@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=richard.henderson@linaro.org \
--cc=sstabellini@kernel.org \
--cc=sunilmut@microsoft.com \
--cc=thuth@redhat.com \
--cc=wenchao.wang@intel.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).