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

On Wed, 28 Aug 2024 16:33:59 -0700, Fenghua Yu wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/2] dmaengine: idxd: Add a new DSA device ID for Granite Rapids-D platform
      commit: f91f2a9879cc77db1f45f690f38f42698580416e
[2/2] dmaengine: idxd: Add new DSA and IAA device IDs for Diamond Rapids platform
      commit: 4fecf944c051ea852e98c062636bf5b4c7f5f8a7

Best regards,
-- 
~Vinod