From: "Michael S. Tsirkin" <mst@redhat.com>
To: Thierry Escande <thierry.escande@vates.tech>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Subject: Re: [PATCH 0/4] ICH9 root PCI hotplug
Date: Wed, 29 Nov 2023 09:54:21 -0500 [thread overview]
Message-ID: <20231129095400-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <be4f338c-7b9e-4bc9-9092-01473ae24548@vates.tech>
On Wed, Nov 29, 2023 at 09:47:13AM +0000, Thierry Escande wrote:
> On 24/11/2023 15:54, Michael S. Tsirkin wrote:
> > On Fri, Nov 24, 2023 at 03:01:35PM +0100, Igor Mammedov wrote:
> > > On Wed, 15 Nov 2023 17:18:53 +0000
> > > Thierry Escande <thierry.escande@vates.tech> wrote:
> > >
> > > > Hi,
> > > >
> > > > This series fixes acpi_hotplug_bridge accessor names, adds new accessors
> > > > for acpi-root-pci-hotplug property, and enables root PCI hotplug by
> > > > default for Q35 machine.
> > >
> > > hotplug on Q35 hostbridge is not implemented intentionally
> > > to keep machine close to the real world.
> >
> > > PCIe spec 3.1a, 1.3.2.3. Root Complex Integrated Endpoint Rules
> > > "
> > > A Root Complex Integrated Endpoint may not be hot-plugged independent of the Root
> > > Complex as a whole.
> > > "
> > > )
> >
> > To be more precise close to native hotplug.
> > But we used ACPI for several years now and it seems to be fine.
> > Maybe it's time we lifted the limitation?
>
> And for what it's worth, lifting this limitation would allow PCIe devices
> passthrough on Q35 VMs with Xen as such devices are hotplugged.
More motivation in the commit log would be a good idea here.
> >
> >
> > >
> > > PS:
> > > but patch 1/4 is good cleanup, pls include Reviewed-by's and resend it
> > > as a separate patch after 8.2 has been released (so it wouldn't get lost in the traffic).
> > >
> > > >
> > > > Thierry Escande (4):
> > > > ich9: Remove unused hotplug field from ICH9LPCPMRegs struct
> > > > ich9: Renamed use_acpi_hotplug_bridge accessors
> > > > ich9: Add accessors for acpi-root-pci-hotplug
> > > > ich9: Enable root PCI hotplug by default
> > > >
> > > > hw/acpi/ich9.c | 23 +++++++++++++++++++++--
> > > > include/hw/acpi/ich9.h | 1 -
> > > > 2 files changed, 21 insertions(+), 3 deletions(-)
> > > >
> >
next prev parent reply other threads:[~2023-11-29 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 17:18 [PATCH 0/4] ICH9 root PCI hotplug Thierry Escande
2023-11-15 17:18 ` [PATCH 2/4] ich9: Renamed use_acpi_hotplug_bridge accessors Thierry Escande
2023-11-15 17:18 ` [PATCH 3/4] ich9: Add accessors for acpi-root-pci-hotplug Thierry Escande
2023-11-15 17:18 ` [PATCH 1/4] ich9: Remove unused hotplug field from ICH9LPCPMRegs struct Thierry Escande
2023-11-15 20:48 ` Philippe Mathieu-Daudé
2023-11-24 13:23 ` Igor Mammedov
2023-11-15 17:18 ` [PATCH 4/4] ich9: Enable root PCI hotplug by default Thierry Escande
2023-11-24 13:37 ` Igor Mammedov
2023-11-24 13:39 ` Igor Mammedov
2023-11-24 14:01 ` [PATCH 0/4] ICH9 root PCI hotplug Igor Mammedov
2023-11-24 14:54 ` Michael S. Tsirkin
2023-11-29 9:47 ` Thierry Escande
2023-11-29 14:54 ` Michael S. Tsirkin [this message]
2023-12-07 17:04 ` Igor Mammedov
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=20231129095400-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=thierry.escande@vates.tech \
/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).