All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] ARM cpu object, setting properties from board model
Date: Tue, 19 Nov 2013 21:16:42 +0100	[thread overview]
Message-ID: <20131119211642.107b84e8@thinkpad> (raw)
In-Reply-To: <CAFEAcA9jtYusaB1dWt_1T28cJdMDOmL4860iT9C3c7ZSii59=A@mail.gmail.com>

On Tue, 19 Nov 2013 20:01:28 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:

> I find myself with a use case where I would like to set
> a CPU object property from the board model init function
> (specifically, I'd like the board model to be able to say
> "this CPU will boot via PSCI so if you're KVM then start
> it appropriately").
> 
> I could just reach in and fiddle with the ARMCPU field
> the way hw/arm/highback.c does with reset_cbar (and in fact
> that's what I'm likely to do for the moment). However it
> seems like it would be nicer for it to be an official
> QOM property. This is alas not currently possible because
> cpu_arm_init() does both 'init' and 'realize', and once
> you've called it it's too late to set properties.
It's possible to use global properties even with cpu_arm_init(),
if it's registered for CPU type before cpu_arm_init() is called.
Than that property would be applied to every new CPU instance
by device_post_init() hook on before object_new() returns.


> 
> Andreas -- did you have any thoughts/plans/code in this area?
> Splitting the realize part out of cpu_arm_init(), or
> providing a cpu_arm_init_dont_realize() [ugh], would be
> easy to code but is it going in the right direction?
> 
> thanks
> -- PMM
> 


-- 
Regards,
  Igor

  parent reply	other threads:[~2013-11-19 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19 20:01 [Qemu-devel] ARM cpu object, setting properties from board model Peter Maydell
2013-11-19 20:12 ` Peter Maydell
2013-11-19 20:16 ` Igor Mammedov [this message]
2013-11-20 15:19 ` Andreas Färber
2013-11-20 15:36   ` Peter Maydell

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=20131119211642.107b84e8@thinkpad \
    --to=imammedo@redhat.com \
    --cc=afaerber@suse.de \
    --cc=peter.maydell@linaro.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.