From: Anthony Liguori <anthony@codemonkey.ws>
To: "Andreas Färber" <afaerber@suse.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 8/7] target-arm: Use IoC for CPU init
Date: Sun, 29 Jan 2012 20:23:39 -0600 [thread overview]
Message-ID: <4F25FF2B.2050600@codemonkey.ws> (raw)
In-Reply-To: <1327881028-9775-1-git-send-email-afaerber@suse.de>
On 01/29/2012 05:50 PM, Andreas Färber wrote:
> Instead of having each CPU's class_init function call its parent's
> function, indirect this through arm_cpu_class_init().
>
> Signed-off-by: Andreas Färber<afaerber@suse.de>
> ---
> target-arm/cpu-core.c | 10 +++++++++-
> 1 files changed, 9 insertions(+), 1 deletions(-)
>
> diff --git a/target-arm/cpu-core.c b/target-arm/cpu-core.c
> index b1ac22c..cdd049e 100644
> --- a/target-arm/cpu-core.c
> +++ b/target-arm/cpu-core.c
> @@ -246,6 +246,13 @@ static void arm_cpu_realize(Object *obj)
> cpu->env.cp15.c0_cpuid = cpu_class->id;
> }
>
> +static void arm_cpu_class_init(ObjectClass *klass, void *data)
> +{
> + const struct ARMCPUDef *d = data;
> +
> + (*d->class_init)(klass, NULL);
> +}
> +
> static void cpu_register(const struct ARMCPUDef *def)
> {
> TypeInfo type = {
> @@ -254,7 +261,8 @@ static void cpu_register(const struct ARMCPUDef *def)
> .instance_size = sizeof(ARMCPU),
> .instance_init = arm_cpu_realize,
> .class_size = sizeof(ARMCPUClass),
> - .class_init = def->class_init,
> + .class_init = arm_cpu_class_init,
> + .class_data = (void *)def,
Would be better IMHO to embed the data needed by class_init in class_data. That
way we're not going through multiple method tables.
Regards,
Anthony Liguori
> };
>
> type_register_static(&type);
next prev parent reply other threads:[~2012-01-30 2:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 13:25 [Qemu-devel] [PATCH RFC 0/7] Introduce QOM CPU and use for target-arm Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH 1/7][RESEND] qom: Introduce object_class_is_abstract() Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 2/7] qom: Register QOM infrastructure early Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 3/7] qom: Add QOM support to user emulators Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 4/7] qom: Introduce CPU class Andreas Färber
2012-01-30 2:14 ` Anthony Liguori
2012-01-30 11:58 ` Andreas Färber
2012-01-31 10:36 ` Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 5/7] cpu: Introduce cpu_class_foreach() Andreas Färber
2012-01-30 2:16 ` Anthony Liguori
2012-01-30 12:02 ` Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 6/7] target-arm: Introduce QOM CPU and use for it CPUID lookup Andreas Färber
2012-01-30 2:19 ` Anthony Liguori
2012-01-30 12:11 ` Andreas Färber
2012-01-29 13:25 ` [Qemu-devel] [PATCH RFC 7/7] target-arm: Embed CPUARMState in QOM ARMCPU Andreas Färber
2012-01-30 2:22 ` Anthony Liguori
2012-01-30 12:52 ` Andreas Färber
2012-01-30 16:01 ` Andreas Färber
2012-01-29 23:50 ` [Qemu-devel] [PATCH RFC 8/7] target-arm: Use IoC for CPU init Andreas Färber
2012-01-30 2:23 ` Anthony Liguori [this message]
2012-01-29 23:50 ` [Qemu-devel] [PATCH RFC 9/7] target-arm: Move CPU feature flags to class Andreas Färber
2012-01-30 19:27 ` Andreas Färber
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=4F25FF2B.2050600@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=afaerber@suse.de \
--cc=qemu-devel@nongnu.org \
/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).