From: Chuck Zmudzinski <brchuckz@aol.com>
To: qemu-devel@nongnu.org
Cc: Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Eduardo Habkost <eduardo@habkost.net>,
xen-devel@lists.xenproject.org
Subject: [PATCH v4 0/2] xen/pt: fix FTBFS and reserve PCI slot 2 for the Intel IGD
Date: Mon, 31 Oct 2022 17:35:51 -0400 [thread overview]
Message-ID: <cover.1667242033.git.brchuckz@aol.com> (raw)
In-Reply-To: cover.1667242033.git.brchuckz.ref@aol.com
This is a series of two patches:
The first fixes FTBFS when --enable-xen and --disable-xen-pci-passthrough
configure options are set with when building for the linux target os.
The second fixes a regression that was introduced many years ago with the
upgrade from the Qemu traditional device model that is still available
from xenbits.xen.org and based on very old Qemu version 0.10.2.
The regression is that the Qemu traditional device model reserves slot 2
for the Intel IGD on the PCI bus when the Intel IGD is passed through
to a Xen HVM domain, but the current Qemu upsream device model does not
and in fact results in a different slot assigned to the Intel IGD.
This behavior does not conform to the requirement that the Intel IGD must
be assigned to slot 2, as noted in docs/igd-assign.txt in the Qemu source
code: "IGD must be given address 02.0 on the PCI root bus in the VM."
I have used the second patch of the series for the past two years with
no problems. Without the patch, the reliability of PCI passthrough of the
Intel IGD to a Xen HVM guest is very poor, and in some cases the guest
fails to start without the patch.
v2: Remove From: <email address> tag at top of message
v3: No change to this cover letter since v2
v4: Use brchuckz@aol.com instead of brchuckz@netscape.net for the author's
email address to match the address used by the same author in commits
be9c61da and c0e86b76
Chuck Zmudzinski (2):
xen/pt: fix syntax error that causes FTBFS in some configurations
xen/pt: reserve PCI slot 2 for Intel igd-passthru
hw/i386/pc_piix.c | 3 +++
hw/xen/meson.build | 2 +-
hw/xen/xen_pt.c | 25 +++++++++++++++++++++++++
hw/xen/xen_pt.h | 16 ++++++++++++++++
hw/xen/xen_pt_stub.c | 4 ++++
5 files changed, 49 insertions(+), 1 deletion(-)
--
2.37.2
next parent reply other threads:[~2022-10-31 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1667242033.git.brchuckz.ref@aol.com>
2022-10-31 21:35 ` Chuck Zmudzinski [this message]
2022-10-31 21:35 ` [PATCH v4 1/2] xen/pt: fix syntax error that causes FTBFS in some configurations Chuck Zmudzinski
2022-10-31 22:08 ` Philippe Mathieu-Daudé
2022-11-02 18:14 ` Laurent Vivier
2022-10-31 21:35 ` [PATCH v4 2/2] xen/pt: reserve PCI slot 2 for Intel igd-passthru Chuck Zmudzinski
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=cover.1667242033.git.brchuckz@aol.com \
--to=brchuckz@aol.com \
--cc=anthony.perard@citrix.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).