On 3 January 2012 14:02, Anthony Liguori <anth...@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
