From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
"qemu devel list" <qemu-devel@nongnu.org>,
"Ani Sinha" <ani@anisinha.ca>, "Ard Biesheuvel" <ardb@kernel.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
qemu-stable@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: Re: [PATCH] acpi: cpuhp: fix guest-visible maximum access size to the legacy reg block
Date: Wed, 1 Mar 2023 08:17:00 +0100 [thread overview]
Message-ID: <CAATJJ0K8Qt3-gNFT4nmweRFk-1bSHGicuLPim_V7EjgaXmLtGw@mail.gmail.com> (raw)
In-Reply-To: <7122894b-ccbf-9d30-ee54-c23c25c0f82b@redhat.com>
On Thu, Jan 5, 2023 at 8:14 AM Laszlo Ersek <lersek@redhat.com> wrote:
>
> On 1/4/23 13:35, Michael S. Tsirkin wrote:
> > On Wed, Jan 04, 2023 at 10:01:38AM +0100, Laszlo Ersek wrote:
> >> The modern ACPI CPU hotplug interface was introduced in the following
> >> series (aa1dd39ca307..679dd1a957df), released in v2.7.0:
> >>
> >> 1 abd49bc2ed2f docs: update ACPI CPU hotplug spec with new protocol
> >> 2 16bcab97eb9f pc: piix4/ich9: add 'cpu-hotplug-legacy' property
> >> 3 5e1b5d93887b acpi: cpuhp: add CPU devices AML with _STA method
> >> 4 ac35f13ba8f8 pc: acpi: introduce AcpiDeviceIfClass.madt_cpu hook
> >> 5 d2238cb6781d acpi: cpuhp: implement hot-add parts of CPU hotplug
> >> interface
> >> 6 8872c25a26cc acpi: cpuhp: implement hot-remove parts of CPU hotplug
> >> interface
> >> 7 76623d00ae57 acpi: cpuhp: add cpu._OST handling
> >> 8 679dd1a957df pc: use new CPU hotplug interface since 2.7 machine type
> >>
...
>
> The solution to the riddle
Hi,
just to add to this nicely convoluted case an FYI to everyone involved
back then,
the fix seems to have caused a regression [1] in - as far as I've
found - an edge case.
[1]: https://gitlab.com/qemu-project/qemu/-/issues/1520
...
> Laszlo
>
>
--
Christian Ehrhardt
Senior Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2023-03-01 7:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 9:01 [PATCH] acpi: cpuhp: fix guest-visible maximum access size to the legacy reg block Laszlo Ersek
2023-01-04 9:33 ` Ard Biesheuvel
2023-01-04 10:26 ` Laszlo Ersek
2023-01-04 9:34 ` Philippe Mathieu-Daudé
2023-01-04 10:29 ` Laszlo Ersek
2023-01-04 10:38 ` Igor Mammedov
2023-01-04 12:27 ` Philippe Mathieu-Daudé
2023-01-04 10:35 ` Igor Mammedov
2023-01-04 12:13 ` Laszlo Ersek
2023-01-04 12:35 ` Michael S. Tsirkin
2023-01-05 7:13 ` Laszlo Ersek
2023-01-05 9:00 ` Philippe Mathieu-Daudé
2023-01-05 9:51 ` Michael S. Tsirkin
2023-03-01 7:17 ` Christian Ehrhardt [this message]
2023-03-01 8:03 ` Laszlo Ersek
2023-03-02 8:32 ` Christian Ehrhardt
2023-03-02 10:38 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2023-01-05 16:18 Laszlo Ersek
2023-01-05 16:21 ` 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=CAATJJ0K8Qt3-gNFT4nmweRFk-1bSHGicuLPim_V7EjgaXmLtGw@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=ani@anisinha.ca \
--cc=ardb@kernel.org \
--cc=imammedo@redhat.com \
--cc=lersek@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--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 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).