From: Igor Mammedov <imammedo@redhat.com>
To: Ani Sinha <ani@anisinha.ca>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
jusual@redhat.com, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: hw/i386/acpi: fix conflicting IO address range for acpi pci hotplug in q35
Date: Tue, 14 Sep 2021 15:00:18 +0200 [thread overview]
Message-ID: <20210914150018.609b39bd@redhat.com> (raw)
In-Reply-To: <20210914045410.3380946-1-ani@anisinha.ca>
On Tue, 14 Sep 2021 10:24:07 +0530
Ani Sinha <ani@anisinha.ca> wrote:
> Hi Igor/Michael :
>
> This patchset fixes the acpi pci hotplug IO address range conflict issue with cpu hotplug.
> This issue has been reported here:
> https://gitlab.com/qemu-project/qemu/-/issues/561
>
> We have disucssed this issue at length here:
> https://lists.gnu.org/archive/html/qemu-devel/2021-09/msg02146.html
>
> This issue affects Qemu version 6.1.
CCing stable
next prev parent reply other threads:[~2021-09-14 13:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-14 4:54 hw/i386/acpi: fix conflicting IO address range for acpi pci hotplug in q35 Ani Sinha
2021-09-14 4:54 ` [PATCH 1/3] bios-tables-test: allow changes in DSDT ACPI tables for q35 Ani Sinha
2021-09-14 12:55 ` Igor Mammedov
2021-09-14 4:54 ` [PATCH 2/3] hw/i386/acpi: fix conflicting IO address range for acpi pci hotplug in q35 Ani Sinha
2021-09-14 12:58 ` Igor Mammedov
2021-09-16 12:59 ` Julia Suvorova
2021-09-14 4:54 ` [PATCH 3/3] bios-tables-test: Update ACPI DSDT table golden blobs for q35 Ani Sinha
2021-09-14 12:58 ` Igor Mammedov
2021-09-14 13:00 ` Igor Mammedov [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-09-16 13:28 hw/i386/acpi: fix conflicting IO address range for acpi pci hotplug in q35 Ani Sinha
2021-09-16 22:56 ` Michael S. Tsirkin
2021-09-17 4:41 ` Ani Sinha
2021-09-17 6:42 ` Ani Sinha
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=20210914150018.609b39bd@redhat.com \
--to=imammedo@redhat.com \
--cc=ani@anisinha.ca \
--cc=jusual@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.