From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcel Apfelbaum <marcel.a@redhat.com>
Cc: "Alexey Kardashevskiy" <aik@ozlabs.ru>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
"Alexander Graf" <agraf@suse.de>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH v5 3/6] vl: allow customizing the class of /machine
Date: Thu, 27 Feb 2014 15:59:17 +0100 [thread overview]
Message-ID: <530F52C5.3080209@redhat.com> (raw)
In-Reply-To: <1393511950.31381.34.camel@localhost.localdomain>
Il 27/02/2014 15:39, Marcel Apfelbaum ha scritto:
>> >
>> > Each of them highlights one of the two aspects that, in my opinion, make
>> > QOM interesting (respectively, unification of interfaces and the
>> > containment tree).
> I was planning to tackle the replacement of the machine from a container
> to an actual object too, however this patch conflicts with my
> series because I already have a QOM Machine object created *always*
> and this patch adds another object *sometimes*.
>
> Is this patch's functionality in use yet? Any idea how to merge those ideas?
pseries simply wants to make /machine implement the FWPathProvider
interface. As long as you have a way for boards to specify a TypeInfo
for /machine, this patch will not get in the way.
Paolo
next prev parent reply other threads:[~2014-02-27 14:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 13:50 [Qemu-devel] [PATCH v5 0/6] spapr: bootindex support Alexey Kardashevskiy
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 1/6] boot: extend get_boot_devices_list() to ignore suffixes Alexey Kardashevskiy
2014-02-20 13:55 ` Paolo Bonzini
2014-02-20 14:03 ` Alexey Kardashevskiy
2014-02-20 14:05 ` Paolo Bonzini
2014-03-13 3:32 ` Alexey Kardashevskiy
2014-03-13 8:00 ` Paolo Bonzini
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 2/6] qdev: introduce FWPathProvider interface Alexey Kardashevskiy
2014-03-12 18:07 ` Andreas Färber
2014-03-12 18:15 ` Paolo Bonzini
2014-03-12 23:02 ` Alexey Kardashevskiy
2014-03-12 23:38 ` Andreas Färber
2014-03-13 1:03 ` Alexey Kardashevskiy
2014-03-13 3:40 ` Alexey Kardashevskiy
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 3/6] vl: allow customizing the class of /machine Alexey Kardashevskiy
2014-02-20 13:58 ` Paolo Bonzini
2014-02-27 10:34 ` Andreas Färber
2014-02-27 10:41 ` Paolo Bonzini
2014-02-27 14:39 ` Marcel Apfelbaum
2014-02-27 14:59 ` Paolo Bonzini [this message]
2014-02-27 15:04 ` Marcel Apfelbaum
2014-02-28 15:03 ` Alexey Kardashevskiy
2014-02-28 15:05 ` Paolo Bonzini
2014-02-28 15:08 ` Alexey Kardashevskiy
2014-02-28 15:57 ` Andreas Färber
2014-02-28 16:35 ` Paolo Bonzini
2014-03-03 10:04 ` Alexey Kardashevskiy
2014-02-21 3:04 ` Alexey Kardashevskiy
2014-02-21 10:30 ` Paolo Bonzini
2014-02-27 2:35 ` Alexey Kardashevskiy
2014-02-27 7:44 ` Markus Armbruster
2014-02-27 11:47 ` Alexey Kardashevskiy
2014-02-27 13:38 ` Markus Armbruster
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 4/6] spapr-llan: add to boot device list Alexey Kardashevskiy
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 5/6] spapr-vio: fix firmware names Alexey Kardashevskiy
2014-02-20 13:50 ` [Qemu-devel] [PATCH v5 6/6] spapr: define interface to fix device pathname Alexey Kardashevskiy
2014-02-20 13:58 ` [Qemu-devel] [PATCH v5 0/6] spapr: bootindex support Paolo Bonzini
2014-02-20 14:05 ` Alexey Kardashevskiy
2014-02-20 14:06 ` Paolo Bonzini
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=530F52C5.3080209@redhat.com \
--to=pbonzini@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=marcel.a@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).