qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrea Bolognani <abologna@redhat.com>
Cc: thuth@redhat.com, lvivier@redhat.com, benh@kernel.crashing.org,
	marcel@redhat.com, aik@ozlabs.ru, groug@kaod.org,
	ehabkost@redhat.com, mdroth@linux.vnet.ibm.com,
	libvir-list@redhat.com, qemu-devel@nongnu.org,
	qemu-ppc@nongnu.org, laine@redhat.com
Subject: Re: [Qemu-devel] Proposal PCI/PCIe device placement on PAPR guests
Date: Mon, 9 Jan 2017 10:46:21 +1100	[thread overview]
Message-ID: <20170108234621.GB12515@umbus.fritz.box> (raw)
In-Reply-To: <1483724069.4199.80.camel@redhat.com>

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

On Fri, Jan 06, 2017 at 06:34:29PM +0100, Andrea Bolognani wrote:
> [Added Laine to CC, fixed qemu-devel address]
> 
> On Thu, 2017-01-05 at 16:46 +1100, David Gibson wrote:
> [...]
> >   * To allow for hotplugged devices, libvirt should also add a number
> >     of additional, empty vPHBs (the PAPR spec allows for hotplug of
> >     PHBs, but this is not yet implemented in qemu).
> 
> "A number" here will have to mean "one", same number of
> empty PCIe Root Ports libvirt will add to a newly-defined
> q35 guest.

Umm.. why?

> >     When hotplugging
> >     a new device (or PE) libvirt should locate a vPHB which doesn't
> >     currently contain anything.
> 
> This will need to be a PHB-specific behavior, because at the
> moment libvirt will happily pick one of the empty slots in
> an existing PHB.

Exactly.  Well, whether it's PHB model specific or machine type
specific is up to you really.  We can only have PAPR PHBs on a PAPR
machine type, so it's kind of arbitrary.

> 
> >   * libvirt should only (automatically) add PHBs - never root ports or
> >     other PCI to PCI bridges
> > 
> > In order to handle migration, the vPHBs will need to be represented in
> > the domain XML, which will also allow the user to override this
> > topology if they want.
> 
> We'll have to decide how to represent them in the XML, but
> that's basically your average bikeshedding.

Right.  Maybe we'd best get started with it, in the hopes of finishing
it in the forseeable future.

> Overall, the plan seems entirely reasonable to me.
> 
> It's pretty clear at this point that pseries guest are
> different enough in their handling of PCI that none of
> the address allocation algorithms currently implemented
> in libvirt could be quite adapted to work with it, so
> a custom one is in order.

Yes, that was my conclusion as well.

-- 
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 --]

  reply	other threads:[~2017-01-09  1:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170105054618.GA12106@umbus.fritz.box>
2017-01-06 12:01 ` [Qemu-devel] Proposal PCI/PCIe device placement on PAPR guests Greg Kurz
2017-01-06 17:34 ` Andrea Bolognani
2017-01-08 23:46   ` David Gibson [this message]
2017-01-12 10:31     ` Andrea Bolognani
2017-01-12 14:52       ` Laine Stump
2017-01-12 16:35         ` Michael Roth
2017-01-12 17:53           ` Laine Stump
2017-01-12 22:56             ` David Gibson
2017-01-18 12:21             ` Marcel Apfelbaum
2017-01-12 22:57       ` David Gibson
2017-01-13 16:29         ` Greg Kurz
     [not found] ` <20170106125758.4643fb35@bahia.lan>
     [not found]   ` <20170112035219.GK14026@umbus.fritz.box>
     [not found]     ` <0bfaa82a-d5f5-eb0f-14a9-f7d13239cee5@ozlabs.ru>
     [not found]       ` <20170112100823.2a906117@bahia.lan>
     [not found]         ` <20170113044831.GP13656@umbus.fritz.box>
     [not found]           ` <20170113095828.302b77f2@bahia.lan>
     [not found]             ` <20170222120825.0253f2d6@bahia.lan>
     [not found]               ` <20170223021152.GR12577@umbus.fritz.box>
2017-02-23  7:23                 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-02-23 22:57                   ` David Gibson

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=20170108234621.GB12515@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=abologna@redhat.com \
    --cc=aik@ozlabs.ru \
    --cc=benh@kernel.crashing.org \
    --cc=ehabkost@redhat.com \
    --cc=groug@kaod.org \
    --cc=laine@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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 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).