From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: aik@ozlabs.ru, qemu-devel@nongnu.org, agraf@suse.de,
ncmike@ncultra.org, qemu-ppc@nongnu.org,
tyreld@linux.vnet.ibm.com, bharata.rao@gmail.com,
nfont@linux.vnet.ibm.com
Subject: Re: [Qemu-devel] [PATCH v6 07/15] spapr_rtas: add ibm, configure-connector RTAS interface
Date: Tue, 03 Mar 2015 23:50:34 -0600 [thread overview]
Message-ID: <20150304055034.27171.34590@loki> (raw)
In-Reply-To: <20150303053339.GN29409@voom.fritz.box>
Quoting David Gibson (2015-03-02 23:33:39)
> On Mon, Mar 02, 2015 at 10:40:16PM -0600, Michael Roth wrote:
> > Quoting David Gibson (2015-03-02 01:02:46)
> > > On Thu, Feb 26, 2015 at 09:11:07PM -0600, Michael Roth wrote:
> > > > This interface is used to fetch an OF device-tree nodes that describes a
> > > > newly-attached device to guest. It is called multiple times to walk the
> > > > device-tree node and fetch individual properties into a 'workarea'/buffer
> > > > provided by the guest.
> > > >
> > > > The device-tree is generated by QEMU and passed to an sPAPRDRConnector during
> > > > the initial hotplug operation, and the state of these RTAS calls is tracked by
> > > > the sPAPRDRConnector. When the last of these properties is successfully
> > > > fetched, we report as special return value to the guest and transition
> > > > the device to a 'configured' state on the QEMU/DRC side.
> > > >
> > > > See docs/specs/ppc-spapr-hotplug.txt for a complete description of
> > > > this interface.
> > > >
> > > > Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> > >
> > >
> > > So, actually, here's probably the best place to explain what I had in
> > > mind for changing the internal interface for this stuff. I was
> > > thinking something like this pseudocode:
> > >
> > > struct DRCCCState {
> > > void *fdt;
> > > int offset;
> > > int depth;
> > > };
> > >
> > > rtas_configure_connector()
> > > {
> > > ...
> > > DRCCCState *ccstate;
> > > ...
> > >
> > > /* check parameters, retrieve drc */
> > > ccstate = drc->ccstate;
> > >
> > > if (!ccstate) {
> > > /* Haven't started configuring yet */
> > > ccstate = malloc(...);
> > > /* Retrieve the dt fragment from the backend */
> > > ccstate->fdt = drck->get_dt(...);
> > > ccstate->offset = 0;
> > > }
> > >
> > > while (get next tag from fdt) {
> > > switch (tag)
> > > case FDT_PROPERTY:
> > > /* Translate property into rtas return values */
> > > return SPAPR_DR_CC_RESPONSE_NEXT_PROPERTY;
> > >
> > > /* other cases ... */
> > > }
> > >
> > > /* Fall through only if we've completed streaming out the dt
> > > */
> > >
> > > /* Tell the back end we've finished configuring */
> > > drck->cc_completed(...);
> > > return SPAPR_DR_CC_RESPONSE_SUCCESS;
> > > }
> > >
> > > On reset, or anything else which interrupts the configuration process,
> > > just blow away drc->ccstate.
> >
> > Ok, that seems reasonable. I took a stab at it here:
> >
> > https://github.com/mdroth/qemu/commit/79ce372743da1b63a6fa33e3de1f1daba8ea1fdc
> > https://github.com/mdroth/qemu/commits/spapr-hotplug-pci
>
> It's looking pretty close now, thanks for the rework.
>
> > It exposes the ccstate as you suggested, via drck->get_cc_state(), and in
> > place of drck->cc_completed() I have drck->set_configured() which serves
> > roughly the same purpose I think. I opted not to let RTAS handle
> > allocation, since it seemed to imply RTAS owns it and not the DRC.
>
> So, that was intentional; basically RTAS *does* own the CCstate. But
> for convenience of index we need connect it to the DRC. Think of it
> like an rtas_priv field in the DRC.
>
> In particular I think the CCstate should be opaque to everything
> except the RTAS code itself, which means initializing the offset and
> depth in RTAS, not in a drck callback. As far as the drck callback
> is concerned, it's supplying a dt fragment, but it doesn't care about
> the details of how the upper layer communicates that through to the
> guest.
Ah ok, so it was about moving the CCState out of DRC, and not just the
awkward interface that wraps FDT traversal. So I went ahead and did it
as you suggested, but also making it actually opaque, and relying on
a couple callbacks that configure-connector passes to
drc->begin_configure_connector to handle init/reset of the CCState
fields (such as the fdt, and the start offset (which isn't necessarilly 0)):
https://github.com/mdroth/qemu/commits/spapr-hotplug-pci
https://github.com/mdroth/qemu/commit/732aa10fa2e41951c396373e7df7d31861322531
I think I have all your other comments addressed, so if that looks ok
I'll post v7 soon. Thanks!
>
> --
> 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
next prev parent reply other threads:[~2015-03-04 5:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 3:11 [Qemu-devel] [PATCH v6 00/15] spapr: add support for pci hotplug Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 01/15] docs: add sPAPR hotplug/dynamic-reconfiguration documentation Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 02/15] spapr_drc: initial implementation of sPAPRDRConnector device Michael Roth
2015-02-27 8:02 ` Bharata B Rao
2015-02-27 9:52 ` Bharata B Rao
2015-02-27 18:30 ` Michael Roth
2015-02-28 9:19 ` Bharata B Rao
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 03/15] spapr_rtas: add get/set-power-level RTAS interfaces Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 04/15] spapr_rtas: add set-indicator RTAS interface Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 05/15] spapr_rtas: add get-sensor-state " Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 06/15] spapr: add rtas_st_buffer_direct() helper Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 07/15] spapr_rtas: add ibm, configure-connector RTAS interface Michael Roth
2015-03-02 7:02 ` David Gibson
2015-03-03 4:40 ` Michael Roth
2015-03-03 5:33 ` David Gibson
2015-03-04 5:50 ` Michael Roth [this message]
2015-03-04 13:37 ` Michael Roth
2015-03-05 4:30 ` David Gibson
2015-03-05 14:12 ` Michael Roth
2015-03-12 5:52 ` David Gibson
2015-03-17 3:31 ` Michael Roth
2015-03-23 0:48 ` David Gibson
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 08/15] spapr_events: re-use EPOW event infrastructure for hotplug events Michael Roth
2015-03-03 5:45 ` David Gibson
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 09/15] spapr_events: event-scan RTAS interface Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 10/15] spapr_drc: add spapr_drc_populate_dt() Michael Roth
2015-03-03 5:52 ` David Gibson
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 11/15] spapr_pci: add dynamic-reconfiguration option for spapr-pci-host-bridge Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 12/15] spapr_pci: create DRConnectors for each PCI slot during PHB realize Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 13/15] pci: make pci_bar useable outside pci.c Michael Roth
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 14/15] spapr_pci: enable basic hotplug operations Michael Roth
2015-03-03 6:08 ` David Gibson
2015-02-27 3:11 ` [Qemu-devel] [PATCH v6 15/15] spapr_pci: emit hotplug add/remove events during hotplug Michael Roth
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=20150304055034.27171.34590@loki \
--to=mdroth@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=bharata.rao@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=ncmike@ncultra.org \
--cc=nfont@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=tyreld@linux.vnet.ibm.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).