From: David Gibson <david@gibson.dropbear.id.au>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: lvivier@redhat.com, thuth@redhat.com,
Peter Krempa <pkrempa@redhat.com>,
aik@ozlabs.ru, qemu-devel@nongnu.org, agraf@suse.de,
Markus Armbruster <armbru@redhat.com>,
pbonzini@redhat.com, abologna@redhat.com,
bharata@linux.vnet.ibm.com, Igor Mammedov <imammedo@redhat.com>,
afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC] QMP: add query-hotpluggable-cpus
Date: Wed, 24 Feb 2016 12:52:19 +1100 [thread overview]
Message-ID: <20160224015219.GE2808@voom.fritz.box> (raw)
In-Reply-To: <20160223212620.GF3901@thinpad.lan.raisama.net>
[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]
On Tue, Feb 23, 2016 at 06:26:20PM -0300, Eduardo Habkost wrote:
> On Tue, Feb 23, 2016 at 10:46:45AM +0100, Igor Mammedov wrote:
> > On Mon, 22 Feb 2016 13:54:32 +1100
> > David Gibson <david@gibson.dropbear.id.au> wrote:
> [...]
> > > This is why Eduardo suggested - and I agreed - that it's probably
> > > better to implement the "1st layer" as an internal structure/interface
> > > only, and implement the 2nd layer on top of that. When/if we need to
> > > we can revisit a user-accessible interface to the 1st layer.
> > We are going around QOM based CPU introspecting interface for
> > years now and that's exactly what 2nd layer is, just another
> > implementation. I've just lost hope in this approach.
> >
> > What I'm suggesting in this RFC is to forget controversial
> > QOM approach for now and use -device/device_add + QMP introspection,
>
> You have a point about it looking controversial, but I would like
> to understand why exactly it is controversial. Discussions seem
> to get stuck every single time we try to do something useful with
> the QOM tree, and I don't undertsand why.
Yeah, I've noticed that too, and I don't know why either.
It's pretty frustrating, since on power we don't have the option of
sticking with the old cpu hotplug interface for now. So I really have
no idea how to move things forwards towards a workable approach.
> > i.e. completely split interface from how boards internally implement
> > CPU hotplug.
>
> A QOM-based interface may still split the interface from how
> boards internally implement CPU hotplug. They don't need to
> affect the device tree of the machine, we just need to create QOM
> objects or links at predictable paths, that implement certain
> interfaces.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-02-24 2:47 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 17:10 [Qemu-devel] [RFC] QMP: add query-hotpluggable-cpus Igor Mammedov
2016-02-15 17:44 ` Eric Blake
2016-02-16 9:58 ` Igor Mammedov
2016-02-15 19:43 ` Markus Armbruster
2016-02-16 5:48 ` David Gibson
2016-02-16 10:52 ` Igor Mammedov
2016-02-18 4:05 ` David Gibson
2016-02-18 10:55 ` Igor Mammedov
2016-02-24 11:26 ` David Gibson
2016-02-24 13:10 ` Igor Mammedov
2016-02-16 10:36 ` Igor Mammedov
2016-02-16 12:35 ` Markus Armbruster
2016-02-16 12:41 ` Andreas Färber
2016-02-16 12:58 ` Markus Armbruster
2016-02-18 3:52 ` David Gibson
2016-02-18 7:33 ` Markus Armbruster
2016-02-17 20:59 ` Eduardo Habkost
2016-02-18 3:39 ` David Gibson
2016-02-18 10:37 ` Igor Mammedov
2016-02-19 4:38 ` David Gibson
2016-02-19 9:51 ` Markus Armbruster
2016-02-19 16:11 ` Igor Mammedov
2016-02-22 2:32 ` David Gibson
2016-02-22 9:05 ` Markus Armbruster
2016-02-24 1:57 ` David Gibson
2016-02-24 8:42 ` Markus Armbruster
2016-02-24 10:51 ` David Gibson
2016-02-24 11:03 ` Igor Mammedov
2016-02-25 1:03 ` David Gibson
2016-02-25 10:22 ` Igor Mammedov
2016-02-19 15:49 ` Igor Mammedov
2016-02-22 2:54 ` David Gibson
2016-02-23 9:46 ` Igor Mammedov
2016-02-23 21:26 ` Eduardo Habkost
2016-02-24 1:52 ` David Gibson [this message]
2016-02-24 14:42 ` Igor Mammedov
2016-02-25 1:05 ` David Gibson
2016-02-25 17:52 ` Eduardo Habkost
2016-02-29 15:42 ` Igor Mammedov
2016-03-01 1:19 ` David Gibson
2016-03-01 10:49 ` Igor Mammedov
2016-03-01 18:17 ` Igor Mammedov
2016-03-01 14:02 ` Eduardo Habkost
2016-02-24 1:54 ` David Gibson
2016-02-24 14:17 ` Igor Mammedov
2016-02-25 1:25 ` David Gibson
2016-02-25 12:43 ` Igor Mammedov
2016-02-26 4:12 ` David Gibson
2016-02-26 10:37 ` Igor Mammedov
2016-02-24 8:53 ` Markus Armbruster
2016-02-24 11:31 ` Igor Mammedov
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=20160224015219.GE2808@voom.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=abologna@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.