From: Paolo Bonzini <pbonzini@redhat.com>
To: "Claudio Fontana" <cfontana@suse.de>,
"Thomas Huth" <thuth@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Stefano Stabellini" <sstabellini@kernel.org>,
"Wenchao Wang" <wenchao.wang@intel.com>,
"Roman Bolshakov" <r.bolshakov@yadro.com>,
"Sunil Muthuswamy" <sunilmut@microsoft.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Paul Durrant <paul@xen.org>, Jason Wang <jasowang@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>,
Dario Faggioli <dfaggioli@suse.com>,
Cameron Esfahani <dirty@apple.com>,
haxm-team@intel.com, Colin Xu <colin.xu@intel.com>,
Anthony Perard <anthony.perard@citrix.com>,
Bruce Rogers <brogers@suse.com>
Subject: Re: [RFC v1 09/10] i386: split cpu.c and defer x86 models registration
Date: Mon, 9 Nov 2020 18:37:06 +0100 [thread overview]
Message-ID: <dd812d5d-061b-de7d-4e43-259a7d3f44ad@redhat.com> (raw)
In-Reply-To: <20201109172755.16500-10-cfontana@suse.de>
On 09/11/20 18:27, Claudio Fontana wrote:
> Defer the x86 models registration to MODULE_INIT_ACCEL_CPU, so that
> accel-specific types can be used as parent types for all cpu models. Use
> the generic TYPE_X86_CPU only if no accel-specific specialization is
> enabled.
Can we use an accel-specific ops struct, and avoid having accel-specific
types? Having dynamic types like these would make it very hard to build
a schema of QOM objects.
Paolo
next prev parent reply other threads:[~2020-11-09 17:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 17:27 [RFC v1 00/10] i386 cleanup Claudio Fontana
2020-11-09 17:27 ` [RFC v1 01/10] i386: move kvm accel files into accel/kvm/ Claudio Fontana
2020-11-09 17:27 ` [RFC v1 02/10] i386: move whpx accel files to accel/whpx/ Claudio Fontana
2020-11-09 17:27 ` [RFC v1 03/10] i386: move hax accel files to accel/hax/ Claudio Fontana
2020-11-09 17:27 ` [RFC v1 04/10] i386: move hvf accel files into accel/hvf/ Claudio Fontana
2020-11-09 17:27 ` [RFC v1 05/10] i386: move TCG accel files into accel/tcg/ Claudio Fontana
2020-11-09 17:27 ` [RFC v1 06/10] i386: move cpu dump out of helper.c into cpu-dump.c Claudio Fontana
2020-11-09 17:27 ` [RFC v1 07/10] i386: move TCG cpu class initialization out of helper.c Claudio Fontana
2020-11-09 17:39 ` Paolo Bonzini
2020-11-10 10:05 ` Claudio Fontana
2020-11-10 10:42 ` Paolo Bonzini
2020-11-09 17:27 ` [RFC v1 08/10] module: introduce MODULE_INIT_ACCEL_CPU Claudio Fontana
2020-11-09 17:27 ` [RFC v1 09/10] i386: split cpu.c and defer x86 models registration Claudio Fontana
2020-11-09 17:34 ` Paolo Bonzini
2020-11-09 17:37 ` Paolo Bonzini [this message]
2020-11-09 18:03 ` Daniel P. Berrangé
2020-11-10 9:40 ` Claudio Fontana
2020-11-10 10:04 ` Daniel P. Berrangé
2020-11-10 10:13 ` Claudio Fontana
2020-11-10 10:41 ` Paolo Bonzini
2020-11-10 15:23 ` Eduardo Habkost
2020-11-10 16:05 ` Paolo Bonzini
2020-11-10 17:55 ` Eduardo Habkost
2020-11-10 20:39 ` Paolo Bonzini
2020-11-10 20:45 ` Eduardo Habkost
2020-11-10 17:38 ` Claudio Fontana
2020-11-10 18:14 ` Eduardo Habkost
2020-11-11 12:59 ` Claudio Fontana
2020-11-16 17:53 ` Claudio Fontana
2020-11-09 19:04 ` Eduardo Habkost
2020-11-10 9:49 ` Claudio Fontana
2020-11-09 17:27 ` [RFC v1 10/10] module: add priority to module_init Claudio Fontana
2020-11-09 17:45 ` [RFC v1 00/10] i386 cleanup no-reply
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=dd812d5d-061b-de7d-4e43-259a7d3f44ad@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=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=paul@xen.org \
--cc=peterx@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.com \
--cc=rth@twiddle.net \
--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).