From: Andrea Bolognani <abologna@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
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: Thu, 12 Jan 2017 11:31:35 +0100 [thread overview]
Message-ID: <1484217095.7948.1.camel@redhat.com> (raw)
In-Reply-To: <20170108234621.GB12515@umbus.fritz.box>
On Mon, 2017-01-09 at 10: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?
Because some applications using libvirt would inevitably
start relying on the fact that such spare PHBs are
available, locking us into providing at least the same
number forever. In other words, increasing the amount at
a later time is always possible, but decreasing it isn't.
We did the same when we started automatically adding PCIe
Root Ports to q35 machines.
The rationale is that having a single spare hotpluggable
slot is extremely convenient for basic usage, eg. a simple
guest created by someone who's not necessarily very
familiar with virtualization; on the other hand, if you
are actually deploying in production you ought to conduct
proper capacity planning and figure out in advance how
many devices you're likely to need to hotplug throughout
the guest's life.
Of course this all will be moot once we can hotplug PHBs :)
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2017-01-12 10:31 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
2017-01-12 10:31 ` Andrea Bolognani [this message]
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=1484217095.7948.1.camel@redhat.com \
--to=abologna@redhat.com \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--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).