qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Maydell <peter.maydell@linaro.org>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: "Chris Wright" <chrisw@redhat.com>,
	quintela@redhat.com,
	"Developers qemu-devel" <qemu-devel@nongnu.org>,
	"KVM devel mailing list" <kvm@vger.kernel.org>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] KVM call agenda for Tuesday 3
Date: Tue, 3 Jan 2012 14:13:15 +0000	[thread overview]
Message-ID: <CAFEAcA_g_bv+LAGgFD806wUrwbBy4zGu8GMmiKMzuz0mATJEdQ@mail.gmail.com> (raw)
In-Reply-To: <4F030A6B.2060809@codemonkey.ws>

On 3 January 2012 14:02, Anthony Liguori <anthony@codemonkey.ws> wrote:
> On 01/03/2012 07:57 AM, Peter Maydell wrote:
>> The CPU should always be a child of the board, surely, even if the user
>> might want to use a different one? That's just basic composition.
>> The links should be for "the CPU has two input IRQ lines" and so on.
>
> Not in the PC world.
>
> You buy a motherboard with an empty CPU socket and then purchase a CPU
> separately and plug it in.
>
> link<> essentially models any type of socket whereas child<> basically means
> "soldered to the board or embedded in silicon".
>
> It may be true for SoCs that CPUs are always child<> but that's not
> universal.

OK, that makes sense, although it leaves me a bit unclear how we
handle the legacy "-cpu" option (clearly useful for users but what it
ought to do to the underlying set of qom objects will vary from machine
to machine...)

-- PMM

  reply	other threads:[~2012-01-03 14:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-02 12:09 [Qemu-devel] KVM call agenda for Tuesday 3 Juan Quintela
2012-01-02 13:46 ` Andreas Färber
2012-01-02 14:11   ` Paolo Bonzini
2012-01-03  1:12     ` Anthony Liguori
2012-01-03  8:54       ` Paolo Bonzini
2012-01-02 15:54   ` Peter Maydell
2012-01-03  1:14     ` Anthony Liguori
2012-01-03 10:26       ` Peter Maydell
2012-01-03 12:07         ` Alex Bradbury
2012-01-03 13:37         ` Anthony Liguori
2012-01-03 13:57           ` Peter Maydell
2012-01-03 14:02             ` Anthony Liguori
2012-01-03 14:13               ` Peter Maydell [this message]
2012-01-03  1:04   ` Anthony Liguori
2012-01-03 13:52     ` Andreas Färber
2012-01-03 13:59       ` Anthony Liguori
2012-01-03  8:33 ` Stefan Hajnoczi
2012-01-03 12:15   ` Dor Laor
2012-01-03 13:12     ` Stefan Hajnoczi
2012-01-03 14:10       ` Andreas Färber
2012-01-03 14:30       ` Vadim Rozenfeld
2012-01-04  2:47       ` Cao,Bing Bu
2012-01-04 11:25         ` Stefan Hajnoczi

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=CAFEAcA_g_bv+LAGgFD806wUrwbBy4zGu8GMmiKMzuz0mATJEdQ@mail.gmail.com \
    --to=peter.maydell@linaro.org \
    --cc=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@redhat.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).