qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Paolo Bonzini <pbonzini@redhat.com>,
	QEMU 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: Tue, 17 Jun 2014 15:16:41 +0800	[thread overview]
Message-ID: <20140617071641.GI16768@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAEgOgz7o3gPxmzRfztkqANdw2jXaOvumh2pCeA41L7NeiDX25w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1246 bytes --]

On Mon, Jun 16, 2014 at 05:46:24PM +1000, Peter Crosthwaite wrote:
> On Mon, Jun 16, 2014 at 5:40 PM, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 10 June 2014 02:32, Alistair Francis <alistair.francis@xilinx.com> wrote:
> >> This patch adds the Cortex-A9 ARM CPU to the A9MPCore.
> >
> > I think this is in general the right way to go.
> >
> >> +    /* Properties for the A9 CPU */
> >> +    DEFINE_PROP_UINT32("midr", A9MPPrivState, midr, 0),
> >> +    DEFINE_PROP_UINT64("reset-cbar", A9MPPrivState, reset_cbar, 0),
> >
> > It seems a bit error-prone if every container object has to manually
> > mirror the properties of the individual CPUs out like this; maybe
> > there's a better way we could come up with?
> >
> > Paolo, weren't you looking at passthrough properties for the
> > virtio devices?
> >
> 
> Stefan added support for QDEV property aliasing.
> 
> http://lists.gnu.org/archive/html/qemu-devel/2014-05/msg06489.html
> 
> The bigger issue though is how do you do an N:1 mapping. The container
> should only have 1 "midr" prop, but it should mirror to all contained
> CPUs. Should we add multiplicity to the aliasing feature?

If we'll need 1:N alias properties in other places too.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-06-17  7:16 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
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 [this message]
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=20140617071641.GI16768@stefanha-thinkpad.redhat.com \
    --to=stefanha@redhat.com \
    --cc=alistair.francis@xilinx.com \
    --cc=pbonzini@redhat.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).