From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 220740] Host crash when do PF passthrough to KVM guest with some devices
Date: Wed, 05 Nov 2025 00:03:02 +0000 [thread overview]
Message-ID: <bug-220740-28872-OFut6o5vJZ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220740-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220740
--- Comment #5 from Alex Williamson (alex.l.williamson@gmail.com) ---
I have an X710, but not a system that can reproduce the issue.
Also I need to correct my previous statement after untangling the headers.
This commit did introduce 8-byte access support for archs including x86_64
where they don't otherwise defined a ioread/write64 support. This access uses
readq/writeq, where previously we'd use pairs or readl/writel. The expectation
is that we're more closely matching the access by the guest.
I'm curious how we're getting into this code for an X710 though, mine shows
BARs as:
03:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for
10GbE SFP+ (rev 01)
Region 0: Memory at 380000000000 (64-bit, prefetchable) [size=8M]
Region 3: Memory at 380001800000 (64-bit, prefetchable) [size=32K]
Those would typically be mapped directly into the KVM address space and not
fault through QEMU to trigger access through this code. The MSI-X capability
lands in BAR3:
Capabilities: [70] MSI-X: Enable- Count=129 Masked-
Vector table: BAR=3 offset=00000000
PBA: BAR=3 offset=00001000
Ideally the device follows the PCIe recommendation not to place registers in
the same page as the vector and pba tables, not doing so could cause this
access though. If it were such an access, QEMU could virtualize the MSI-X
tables on a different BAR with the option x-msix-relocation=bar5 (or bar2).
If QEMU were using x-no-mmap=on then we could expect this code would be used,
but that's not specified in the example.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-11-05 0:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 9:12 [Bug 220740] New: Host crash when do PF passthrough to KVM guest with some devices bugzilla-daemon
2025-11-03 9:17 ` [Bug 220740] " bugzilla-daemon
2025-11-03 23:47 ` bugzilla-daemon
2025-11-04 5:48 ` bugzilla-daemon
2025-11-04 5:53 ` bugzilla-daemon
2025-11-05 0:03 ` bugzilla-daemon [this message]
2025-12-09 2:54 ` Tian, Kevin
2025-11-05 4:06 ` bugzilla-daemon
2025-11-05 8:12 ` bugzilla-daemon
2025-12-09 2:54 ` bugzilla-daemon
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=bug-220740-28872-OFut6o5vJZ@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=kvm@vger.kernel.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).