From: Laszlo Ersek <lersek@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: "Ard Biesheuvel (kernel.org address)" <ardb@kernel.org>,
qemu devel list <qemu-devel@nongnu.org>
Subject: Re: IO port write width clamping differs between TCG and KVM
Date: Wed, 4 Jan 2023 07:06:03 +0100 [thread overview]
Message-ID: <ea401dd3-53f1-b27c-4a5a-9085ce5ab051@redhat.com> (raw)
In-Reply-To: <aaedee84-d3ed-a4f9-21e7-d221a28d1683@redhat.com>
On 1/3/23 18:42, Laszlo Ersek wrote:
> (resending with qemu-devel on CC; sorry!)
>
> Hi,
>
> this is with QEMU-7.2.
This is a regression. It works fine with QEMU-5.0. The regression has
not been fixed since QEMU-7.2, as of master @ 222059a0fccf ("Merge tag
'pull-ppc-20221221' of https://gitlab.com/danielhb/qemu into staging",
2022-12-21).
I'm bisecting.
(It's a relief that this is a regression. I felt pretty certain that I
had tested CPU hotplug with TCG as well!
I've picked QEMU-5.0 as the start candidate for my bisection for the
following reason: per git-blame, Igor described the modern interface
detection steps in commit ae340aa3d2567 (which I reviewed), and the
first tag/release to contain that commit was QEMU-5.0. The first QEMU
release after Igor and I had worked on this in QEMU and OVMF definitely
worked with TCG too, by my account.)
Laszlo
next prev parent reply other threads:[~2023-01-04 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-03 17:42 IO port write width clamping differs between TCG and KVM Laszlo Ersek
2023-01-04 6:06 ` Laszlo Ersek [this message]
2023-01-04 6:16 ` Laszlo Ersek
2023-01-04 7:04 ` Laszlo Ersek
2023-01-04 7:23 ` Philippe Mathieu-Daudé
2023-01-04 10: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=ea401dd3-53f1-b27c-4a5a-9085ce5ab051@redhat.com \
--to=lersek@redhat.com \
--cc=ardb@kernel.org \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--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).