From: Bjorn Helgaas <helgaas@kernel.org>
To: Alex Williamson <alex.williamson@redhat.com>,
Peter Xu <peterx@redhat.com>,
Athul Krishna <athul.krishna.kr@protonmail.com>
Cc: kvm@vger.kernel.org, linux-pci@vger.kernel.org,
regressions@lists.linux.dev
Subject: [bugzilla-daemon@kernel.org: [Bug 219619] New: vfio-pci: screen graphics artifacts after 6.12 kernel upgrade]
Date: Sun, 22 Dec 2024 16:36:04 -0600 [thread overview]
Message-ID: <20241222223604.GA3735586@bhelgaas> (raw)
Forwarding since not everybody follows bugzilla. Apparently bisected
to f9e54c3a2f5b ("vfio/pci: implement huge_fault support").
Athul, f9e54c3a2f5b appears to revert cleanly from v6.13-rc1. Can you
verify that reverting it is enough to avoid these artifacts?
#regzbot introduced: f9e54c3a2f5b ("vfio/pci: implement huge_fault support")
----- Forwarded message from bugzilla-daemon@kernel.org -----
Date: Sat, 21 Dec 2024 10:10:02 +0000
From: bugzilla-daemon@kernel.org
To: bjorn@helgaf9e54c3a2f5bas.com
Subject: [Bug 219619] New: vfio-pci: screen graphics artifacts after 6.12 kernel upgrade
Message-ID: <bug-219619-41252@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=219619
Bug ID: 219619
Summary: vfio-pci: screen graphics artifacts after 6.12 kernel
upgrade
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: PCI
Assignee: drivers_pci@kernel-bugs.osdl.org
Reporter: athul.krishna.kr@protonmail.com
Regression: No
Created attachment 307382
--> https://bugzilla.kernel.org/attachment.cgi?id=307382&action=edit
dmesg
Device: Asus Zephyrus GA402RJ
CPU: Ryzen 7 6800HS
GPU: RX 6700S
Kernel: 6.13.0-rc3-g8faabc041a00
Problem:
Launching games or gpu bench-marking tools in qemu windows 11 vm will cause
screen artifacts, ultimately qemu will pause with unrecoverable error.
Commit:
f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101 is the first bad commit
commit f9e54c3a2f5b79ecc57c7bc7d0d3521e461a2101
Author: Alex Williamson <alex.williamson@redhat.com>
Date: Mon Aug 26 16:43:53 2024 -0400
vfio/pci: implement huge_fault support
With the addition of pfnmap support in vmf_insert_pfn_{pmd,pud}() we can
take advantage of PMD and PUD faults to PCI BAR mmaps and create more
efficient mappings. PCI BARs are always a power of two and will typically
get at least PMD alignment without userspace even trying. Userspace
alignment for PUD mappings is also not too difficult.
Consolidate faults through a single handler with a new wrapper for
standard single page faults. The pre-faulting behavior of commit
d71a989cf5d9 ("vfio/pci: Insert full vma on mmap'd MMIO fault") is removed
in this refactoring since huge_fault will cover the bulk of the faults and
results in more efficient page table usage. We also want to avoid that
pre-faulted single page mappings preempt huge page mappings.
Link: https://lkml.kernel.org/r/20240826204353.2228736-20-peterx@redhat.com
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Signed-off-by: Peter Xu <peterx@redhat.com>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Aneesh Kumar K.V <aneesh.kumar@linux.ibm.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Catalin Marinas <catalin.marinas@arm.com>
Cc: Christian Borntraeger <borntraeger@linux.ibm.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: Gavin Shan <gshan@redhat.com>
Cc: Gerald Schaefer <gerald.schaefer@linux.ibm.com>
Cc: Heiko Carstens <hca@linux.ibm.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>
Cc: Matthew Wilcox <willy@infradead.org>
Cc: Niklas Schnelle <schnelle@linux.ibm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Ryan Roberts <ryan.roberts@arm.com>
Cc: Sean Christopherson <seanjc@google.com>
Cc: Sven Schnelle <svens@linux.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Cc: Will Deacon <will@kernel.org>
Cc: Zi Yan <ziy@nvidia.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
drivers/vfio/pci/vfio_pci_core.c | 60 ++++++++++++++++++++++++++++------------
1 file changed, 43 insertions(+), 17 deletions(-)
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
----- End forwarded message -----
next reply other threads:[~2024-12-22 22:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 22:36 Bjorn Helgaas [this message]
2024-12-23 7:37 ` [bugzilla-daemon@kernel.org: [Bug 219619] New: vfio-pci: screen graphics artifacts after 6.12 kernel upgrade] Athul Krishna
2024-12-23 16:59 ` Peter Xu
2024-12-23 18:15 ` Alex Williamson
2024-12-24 18:06 ` Athul Krishna
2024-12-30 21:03 ` Precific
2024-12-31 1:27 ` Alex Williamson
2024-12-31 15:44 ` Precific
2024-12-31 16:07 ` Alex Williamson
2025-01-01 3:10 ` Precific
2025-01-02 16:39 ` Peter Xu
2025-01-02 17:04 ` Alex Williamson
2025-01-02 18:38 ` Alex Williamson
2025-02-25 17:59 ` Bjorn Helgaas
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=20241222223604.GA3735586@bhelgaas \
--to=helgaas@kernel.org \
--cc=alex.williamson@redhat.com \
--cc=athul.krishna.kr@protonmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=regressions@lists.linux.dev \
/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