From: "Michael S. Tsirkin" <mst@redhat.com>
To: Julia Suvorova <jusual@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [RFC PATCH v2 0/4] Use ACPI PCI hot-plug for q35
Date: Thu, 20 Aug 2020 23:41:31 -0400 [thread overview]
Message-ID: <20200820234019-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20200818215227.181654-1-jusual@redhat.com>
On Tue, Aug 18, 2020 at 11:52:23PM +0200, Julia Suvorova wrote:
> PCIe native hot-plug has numerous problems with racing events and unpredictable
> guest behaviour (Windows). Switching to ACPI hot-plug for now.
>
> Tested on RHEL 8 and Windows 2019.
> pxb-pcie is not yet supported.
Julia, pls update expected acpi tables, see tests/qtest/bios-tables-test.c
> v2:
> * new ioport range for acpiphp [Gerd]
> * drop find_pci_host() [Igor]
> * explain magic numbers in _OSC [Igor]
> * drop build_q35_pci_hotplug() wrapper [Igor]
>
> Julia Suvorova (4):
> hw/acpi/ich9: Trace ich9_gpe_readb()/writeb()
> hw/i386/acpi-build: Add ACPI PCI hot-plug methods to q35
> hw/i386/acpi-build: Turn off support of PCIe native hot-plug and SHPC
> in _OSC
> hw/acpi/ich9: Enable ACPI PCI hot-plug
>
> hw/i386/acpi-build.h | 12 ++++++++++
> include/hw/acpi/ich9.h | 3 +++
> include/hw/acpi/pcihp.h | 3 ++-
> hw/acpi/ich9.c | 52 ++++++++++++++++++++++++++++++++++++++++-
> hw/acpi/pcihp.c | 15 ++++++++----
> hw/acpi/piix4.c | 2 +-
> hw/i386/acpi-build.c | 48 +++++++++++++++++++++++--------------
> hw/i386/pc.c | 1 +
> hw/acpi/trace-events | 4 ++++
> 9 files changed, 114 insertions(+), 26 deletions(-)
>
> --
> 2.25.4
next prev parent reply other threads:[~2020-08-21 3:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-18 21:52 [RFC PATCH v2 0/4] Use ACPI PCI hot-plug for q35 Julia Suvorova
2020-08-18 21:52 ` [RFC PATCH v2 1/4] hw/acpi/ich9: Trace ich9_gpe_readb()/writeb() Julia Suvorova
2020-08-19 3:14 ` Philippe Mathieu-Daudé
2020-08-25 13:14 ` Julia Suvorova
2020-08-18 21:52 ` [RFC PATCH v2 2/4] hw/i386/acpi-build: Add ACPI PCI hot-plug methods to q35 Julia Suvorova
2020-08-19 3:21 ` Philippe Mathieu-Daudé
2020-09-16 19:24 ` Julia Suvorova
2020-08-21 12:08 ` Igor Mammedov
2020-09-16 19:02 ` Julia Suvorova
2020-08-18 21:52 ` [RFC PATCH v2 3/4] hw/i386/acpi-build: Turn off support of PCIe native hot-plug and SHPC in _OSC Julia Suvorova
2020-08-21 12:13 ` Igor Mammedov
2020-09-16 18:03 ` Julia Suvorova
2020-09-16 19:14 ` Julia Suvorova
2020-09-17 6:01 ` Igor Mammedov
2020-09-17 10:40 ` Julia Suvorova
2020-09-18 6:50 ` Igor Mammedov
2020-08-18 21:52 ` [RFC PATCH v2 4/4] hw/acpi/ich9: Enable ACPI PCI hot-plug Julia Suvorova
2020-08-21 12:24 ` Igor Mammedov
2020-09-16 19:28 ` Julia Suvorova
2020-08-18 22:29 ` [RFC PATCH v2 0/4] Use ACPI PCI hot-plug for q35 no-reply
2020-08-21 3:41 ` Michael S. Tsirkin [this message]
2020-08-21 10:30 ` Igor Mammedov
2020-08-21 12:29 ` Igor Mammedov
2020-08-22 14:25 ` Laszlo Ersek
2020-08-24 11:35 ` Igor Mammedov
2020-08-24 11:51 ` Ani Sinha
2020-08-24 15:03 ` Laszlo Ersek
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=20200820234019-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=imammedo@redhat.com \
--cc=jusual@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@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).