From: Marcel Apfelbaum <marcel@redhat.com>
To: Laine Stump <laine@redhat.com>, libvir-list@redhat.com
Cc: Michael Roth <mdroth@linux.vnet.ibm.com>,
Andrea Bolognani <abologna@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
thuth@redhat.com, lvivier@redhat.com, benh@kernel.crashing.org,
aik@ozlabs.ru, groug@kaod.org, ehabkost@redhat.com,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Alex Williamson <Alex.Williamson@redhat.com>
Subject: Re: [Qemu-devel] Proposal PCI/PCIe device placement on PAPR guests
Date: Wed, 18 Jan 2017 14:21:09 +0200 [thread overview]
Message-ID: <f083c54a-abbf-32c2-c0cf-d95881e4b2b0@redhat.com> (raw)
In-Reply-To: <75e2809a-dab3-15f8-d125-3d2def5ebeeb@redhat.com>
On 01/12/2017 07:53 PM, Laine Stump wrote:
> On 01/12/2017 11:35 AM, Michael Roth wrote:
>> Quoting Laine Stump (2017-01-12 08:52:10)
[...]
>
>
> Yeah you're right, I'm probably remembering the wrong problem and wrong reason for the problem. I just remember there was *some* issue about hotplugging new PCI controllers. Possibly the internal
> representation of the bus hierarchy wasn't updated unless you forced a rescan of all the devices or something? My memory of it is vague, I just remember being told it wasn't just a case of the
> controller itself being initialized.
>
> Alex or Marcel - since whatever it was I likely heard it from one of you (or imagined it in a dream), can you straighten me out?
>
Hi Laine,
Indeed, hot-plugging a QEMU pci-bridge in X86 is somehow problematic since
it comes with some bits on ACPI tables which are already loaded at hot-plug time.
We need the bits since the x86 pci-hotplug is ACPI based. For Q35 machine might be easier,
but is not implemented yet as far as I know.
Thanks,
Marcel
[...]
next prev parent reply other threads:[~2017-01-18 12:21 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
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 [this message]
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=f083c54a-abbf-32c2-c0cf-d95881e4b2b0@redhat.com \
--to=marcel@redhat.com \
--cc=Alex.Williamson@redhat.com \
--cc=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=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).