qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Cc: mdroth@linux.ibm.com, groug@kaod.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 0/8] pseries: Allow hotplug of P2P bridges and devices under P2P bridges
Date: Mon, 3 Jun 2019 15:04:18 +1000	[thread overview]
Message-ID: <20190603050417.GA3285@umbus> (raw)
In-Reply-To: <20190530053831.22115-1-david@gibson.dropbear.id.au>

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

On Thu, May 30, 2019 at 03:38:23PM +1000, David Gibson wrote:
> PAPR has its own PCI hotplug mechanism which we implemented quite a
> while ago.  However, we weren't able to hotplug devices under PCI
> bridges, because the pci-bridge code would try to handle the hotplug
> using SHPC which won't work with PAPR.
> 
> We now have the infrastructure in the hotplug core to have the machine
> take control of the hotplug before the bus tries to claim it, which
> lets us address this.  While we're about it, make a bunch of cleanups
> and also allow hot plug of P2P bridges themselves (this turns out to
> be quite straightforward once the rest is in place).
> 
> For now, we don't support hot unplug of bridges - this seems to cause
> problems, at least for a Linux guest.  I suspect the problem is on the
> guest side, but for now just prohibit until we have time to
> investigate properly.

I've fixed the problem Alexey pointed out, and I've merged this
tentatively to the ppc-for-4.1 branch.

> 
> Changes since v1:
>  * Added proper cover letter
>  * Addressed some minor comments
> 
> David Gibson (8):
>   spapr: Clean up device node name generation for PCI devices
>   spapr: Clean up device tree construction for PCI devices
>   spapr: Clean up dt creation for PCI buses
>   spapr: Clean up spapr_drc_populate_dt()
>   spapr: Clean up DRC index construction
>   spapr: Don't use bus number for building DRC ids
>   spapr: Direct all PCI hotplug to host bridge, rather than P2P bridge
>   spapr: Allow hot plug/unplug of PCI bridges and devices under PCI
>     bridges
> 
>  hw/ppc/spapr.c              |  25 +-
>  hw/ppc/spapr_drc.c          |  13 +-
>  hw/ppc/spapr_pci.c          | 486 ++++++++++++++++++++++--------------
>  include/hw/pci-host/spapr.h |   4 +-
>  include/hw/ppc/spapr_drc.h  |   3 +-
>  5 files changed, 327 insertions(+), 204 deletions(-)
> 

-- 
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: 833 bytes --]

      parent reply	other threads:[~2019-06-03  7:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-30  5:38 [Qemu-devel] [PATCH v2 0/8] pseries: Allow hotplug of P2P bridges and devices under P2P bridges David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 1/8] spapr: Clean up device node name generation for PCI devices David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 2/8] spapr: Clean up device tree construction " David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 3/8] spapr: Clean up dt creation for PCI buses David Gibson
2019-05-31  4:45   ` Alexey Kardashevskiy
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 4/8] spapr: Clean up spapr_drc_populate_dt() David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 5/8] spapr: Clean up DRC index construction David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 6/8] spapr: Don't use bus number for building DRC ids David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 7/8] spapr: Direct all PCI hotplug to host bridge, rather than P2P bridge David Gibson
2019-05-30  5:38 ` [Qemu-devel] [PATCH v2 8/8] spapr: Allow hot plug/unplug of PCI bridges and devices under PCI bridges David Gibson
2019-06-03  5:04 ` David Gibson [this message]

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=20190603050417.GA3285@umbus \
    --to=david@gibson.dropbear.id.au \
    --cc=groug@kaod.org \
    --cc=mdroth@linux.ibm.com \
    --cc=mst@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).