mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kevin Tian <kevin.tian@intel.com>
To: Alex Williamson <alex@shazbot.org>, Ankit Agrawal <ankita@nvidia.com>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Yishai Hadas <yishaih@nvidia.com>,
	Shameer Kolothum <skolothumtho@nvidia.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Ramesh Thomas <ramesh.thomas@intel.com>,
	Yunxiang Li <Yunxiang.Li@amd.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] vfio/pci: Fix issues with qword access
Date: Thu, 18 Dec 2025 08:16:48 +0000	[thread overview]
Message-ID: <20251218081650.555015-1-kevin.tian@intel.com> (raw)

Certain devices (e.g. Intel X710) don't support qword access to the
rom bar, otherwise PCI aer errors are observed. Fix it by disabling
the qword access to the rom bar.

While at it, also restrict accesses to the legacy VGA resource to
dword. More for paranoia so stable kernel is not CC-ed.

v2:
- Rebase to 6.19-rc1
- Use enum to avoid adding another bool arg (Alex)
- Elaborate the commit msg (Alex)
- New patch to disallow qword access to legacy VGA (Alex)

v1:
https://lore.kernel.org/all/20251212020941.338355-1-kevin.tian@intel.com/

Kevin Tian (2):
  vfio/pci: Disable qword access to the PCI ROM bar
  vfio/pci: Disable qword access to the VGA region

 drivers/vfio/pci/nvgrace-gpu/main.c |  4 ++--
 drivers/vfio/pci/vfio_pci_rdwr.c    | 25 ++++++++++++++++++-------
 include/linux/vfio_pci_core.h       | 10 +++++++++-
 3 files changed, 29 insertions(+), 10 deletions(-)

-- 
2.43.0


             reply	other threads:[~2025-12-18  8:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18  8:16 Kevin Tian [this message]
2025-12-18  8:16 ` [PATCH v2 1/2] vfio/pci: Disable qword access to the PCI ROM bar Kevin Tian
2025-12-18  9:20   ` Chen, Farrah
2025-12-18  8:16 ` [PATCH v2 2/2] vfio/pci: Disable qword access to the VGA region Kevin Tian
2025-12-23 23:41 ` [PATCH v2 0/2] vfio/pci: Fix issues with qword access Alex Williamson

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=20251218081650.555015-1-kevin.tian@intel.com \
    --to=kevin.tian@intel.com \
    --cc=Yunxiang.Li@amd.com \
    --cc=alex@shazbot.org \
    --cc=ankita@nvidia.com \
    --cc=jgg@ziepe.ca \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ramesh.thomas@intel.com \
    --cc=skolothumtho@nvidia.com \
    --cc=yishaih@nvidia.com \
    /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

all inboxes | Powered by JetHome®