From: Olaf Hering <olaf@aepfle.de>
To: Bernhard Beschow <shentey@gmail.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
John Snow <jsnow@redhat.com>,
xen-devel@lists.xenproject.org,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v2] piix: fix regression during unplug in Xen HVM domUs
Date: Tue, 27 Jun 2023 13:40:28 +0200 [thread overview]
Message-ID: <20230627134028.648924f4.olaf@aepfle.de> (raw)
In-Reply-To: <5DB37FA5-41DF-4ED6-8C8A-CDDD6F276F42@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 397 bytes --]
Tue, 27 Jun 2023 10:12:50 +0000 Bernhard Beschow <shentey@gmail.com>:
> Bits 4..15 represent the BAR address, and pci_set_byte() only clears bits 4..7, leaving bits 8..15 unchanged. Perhaps this causes the BAR to be moved into the UHCI region? Does changing the call to pci_set_long() fix the problem?
Thanks, it seems this fixes the issue. Let me verify this with a clean build.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-27 11:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 7:00 [PATCH v2] piix: fix regression during unplug in Xen HVM domUs Olaf Hering
2021-03-22 22:09 ` John Snow
2021-03-25 11:12 ` Olaf Hering
2021-03-25 16:49 ` Paolo Bonzini
2023-05-09 22:58 ` Olaf Hering
2023-05-10 7:47 ` Olaf Hering
2023-05-12 21:12 ` Stefano Stabellini
2023-05-16 17:38 ` John Snow
2023-05-16 20:00 ` Olaf Hering
2023-06-26 21:19 ` Olaf Hering
2023-06-27 7:11 ` Paolo Bonzini
2023-06-27 10:12 ` Bernhard Beschow
2023-06-27 11:40 ` Olaf Hering [this message]
2023-06-27 12:07 ` Olaf Hering
2023-06-28 9:27 ` Bernhard Beschow
2023-06-30 7:29 ` Olaf Hering
2023-06-30 8:05 ` Bernhard Beschow
2023-06-30 11:32 ` Olaf Hering
2023-06-30 22:15 ` Bernhard Beschow
2023-06-30 8:48 ` Paolo Bonzini
2023-07-01 9:53 ` Bernhard Beschow
2023-07-01 11:58 ` Mark Cave-Ayland
2023-07-02 22:25 ` Bernhard Beschow
2023-06-27 11:32 ` Olaf Hering
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=20230627134028.648924f4.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=shentey@gmail.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.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).