qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
	Alistair Francis <alistair.francis@xilinx.com>
Subject: Re: [Qemu-devel] [RFC v1 1/2] arm: Add the cortex-a9 CPU to the a9mpcore device
Date: Mon, 16 Jun 2014 13:18:47 +0200	[thread overview]
Message-ID: <539ED297.8050308@suse.de> (raw)
In-Reply-To: <CAFEAcA_M6N5tBm3fPsAz0uC=NHP9Z-7VoxkyNgcP9dvZne=v0Q@mail.gmail.com>

Am 16.06.2014 12:44, schrieb Peter Maydell:
> On 16 June 2014 11:19, Andreas Färber <afaerber@suse.de> wrote:
>> Am 16.06.2014 06:43, schrieb Peter Crosthwaite:
>>> So you could add an integer property listener to init them earlier (or
>>> even do dynamic extending/freeing or the allocated CPUs). I'm not sure
>>> exactly what we are really supposed to do though, when the number of
>>> child object depends on a prop like this? Andreas?
>>
>> PMM had added or looked into a property creating an array of properties.
>> However a more fundamental issue that PMM was unsure about is whether
>> the CPUs should be child<> of MPCore as done here or a sibling of the
>> MPCore container.
> 
> Was I? I can't currently see any reason you'd want them to be
> siblings of the container rather than children...
> 
> I think property-listeners was the mechanism we talked
> about for when you need to do something before realize
> but it depends on some property, yes.

Got a pointer to that? Waiting for review or merged in my absence?

Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2014-06-16 11:18 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  1:32 [Qemu-devel] [RFC v1 1/2] arm: Add the cortex-a9 CPU to the a9mpcore device Alistair Francis
2014-06-10  1:33 ` [Qemu-devel] [RFC v1 2/2] zynq: Update Zynq to init the CPU in " Alistair Francis
2014-06-16  4:42   ` Peter Crosthwaite
2014-06-16  6:50     ` Alistair Francis
2014-06-16  1:17 ` [Qemu-devel] [RFC v1 1/2] arm: Add the cortex-a9 CPU to " Alistair Francis
2014-06-16  4:43 ` Peter Crosthwaite
2014-06-16  6:04   ` Alistair Francis
2014-06-16 10:26     ` Andreas Färber
2014-06-16 10:19   ` Andreas Färber
2014-06-16 10:34     ` Peter Crosthwaite
2014-06-16 10:58       ` Andreas Färber
2014-06-16 11:11         ` Peter Maydell
2014-06-16 11:17           ` Andreas Färber
2014-06-16 11:22           ` Peter Crosthwaite
2014-06-16 11:23             ` Andreas Färber
2014-06-16 10:44     ` Peter Maydell
2014-06-16 11:18       ` Andreas Färber [this message]
2014-06-16 11:20         ` Peter Maydell
2014-06-16  7:40 ` Peter Maydell
2014-06-16  7:46   ` Peter Crosthwaite
2014-06-17  7:16     ` Stefan Hajnoczi
2014-06-17  8:05       ` Paolo Bonzini
2014-06-17 10:12         ` Peter Crosthwaite
2014-06-17 23:33           ` Alistair Francis

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=539ED297.8050308@suse.de \
    --to=afaerber@suse.de \
    --cc=alistair.francis@xilinx.com \
    --cc=peter.crosthwaite@xilinx.com \
    --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 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).