From: Fenghua Yu <fenghua.yu@intel.com>
To: "Vinod Koul" <vkoul@kernel.org>, "Dave Jiang" <dave.jiang@intel.com>
Cc: dmaengine@vger.kernel.org,
"linux-kernel" <linux-kernel@vger.kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>
Subject: [PATCH v2 0/2] Add a few new DSA/IAA device IDs
Date: Wed, 28 Aug 2024 16:33:59 -0700 [thread overview]
Message-ID: <20240828233401.186007-1-fenghua.yu@intel.com> (raw)
Due to a potential security issue, it's not safe to assign legacy
DSA/IAA devices to virtual machines. This issue has been addressed
by adding the legacy DSA/IAA device IDs to the VFIO denylist[1].
With the security issue fixed in newer DSA/IAA devices, which have
new device IDs, these devices can be safely assigned to virtual
machines without needing to add their IDs to the VFIOI denylist.
Additionally, the new device IDs may be useful to identify any other
potential issues with specific device as well in the future.
[1] commit 95feb3160eef ("VFIO: Add the SPR_DSA and SPR_IAX devices to
the denylist")
Fenghua Yu (2):
dmaengine: idxd: Add a new DSA device ID for Granite Rapids-D platform
dmaengine: idxd: Add new DSA and IAA device IDs for Diamond Rapids
platform
drivers/dma/idxd/init.c | 6 ++++++
include/linux/pci_ids.h | 3 +++
2 files changed, 9 insertions(+)
--
2.37.1
next reply other threads:[~2024-08-28 23:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-28 23:33 Fenghua Yu [this message]
2024-08-28 23:34 ` [PATCH v2 1/2] dmaengine: idxd: Add a new DSA device ID for Granite Rapids-D platform Fenghua Yu
2024-08-28 23:34 ` [PATCH v2 2/2] dmaengine: idxd: Add new DSA and IAA device IDs for Diamond Rapids platform Fenghua Yu
2024-08-28 23:37 ` Dave Jiang
2024-08-29 17:30 ` [PATCH v2 0/2] Add a few new DSA/IAA device IDs Vinod Koul
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=20240828233401.186007-1-fenghua.yu@intel.com \
--to=fenghua.yu@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@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