linux-kernel - Re: [PATCH v8 00/14] iommufd: Add vIOMMU infrastructure (Part-3: vEVENTQ)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Z8KPtlAy1aekFe2C@Asurada-Nvidia>
Date: Fri, 28 Feb 2025 20:40:22 -0800
From: Nicolin Chen <nicolinc@...dia.com>
To: Zhangfei Gao <zhangfei.gao@...aro.org>
CC: <jgg@...dia.com>, <kevin.tian@...el.com>, <corbet@....net>,
	<will@...nel.org>, <joro@...tes.org>, <suravee.suthikulpanit@....com>,
	<robin.murphy@....com>, <dwmw2@...radead.org>, <baolu.lu@...ux.intel.com>,
	<linux-kernel@...r.kernel.org>, <iommu@...ts.linux.dev>,
	<linux-arm-kernel@...ts.infradead.org>, <linux-kselftest@...r.kernel.org>,
	<linux-doc@...r.kernel.org>, <eric.auger@...hat.com>,
	<jean-philippe@...aro.org>, <mdf@...nel.org>, <mshavit@...gle.com>,
	<shameerali.kolothum.thodi@...wei.com>, <smostafa@...gle.com>,
	<ddutile@...hat.com>, <yi.l.liu@...el.com>, <praan@...gle.com>,
	<patches@...ts.linux.dev>
Subject: Re: [PATCH v8 00/14] iommufd: Add vIOMMU infrastructure (Part-3:
 vEVENTQ)

On Sat, Mar 01, 2025 at 12:16:00PM +0800, Zhangfei Gao wrote:
> On Wed, 26 Feb 2025 at 01:33, Nicolin Chen <nicolinc@...dia.com> wrote:
> >
> > As the vIOMMU infrastructure series part-3, this introduces a new vEVENTQ
> > object. The existing FAULT object provides a nice notification pathway to
> > the user space with a queue already, so let vEVENTQ reuse that.
> >
> > Mimicing the HWPT structure, add a common EVENTQ structure to support its
> > derivatives: IOMMUFD_OBJ_FAULT (existing) and IOMMUFD_OBJ_VEVENTQ (new).
> >
> > An IOMMUFD_CMD_VEVENTQ_ALLOC is introduced to allocate vEVENTQ object for
> > vIOMMUs. One vIOMMU can have multiple vEVENTQs in different types but can
> > not support multiple vEVENTQs in the same type.
> >
> > The forwarding part is fairly simple but might need to replace a physical
> > device ID with a virtual device ID in a driver-level event data structure.
> > So, this also adds some helpers for drivers to use.
> >
> > As usual, this series comes with the selftest coverage for this new ioctl
> > and with a real world use case in the ARM SMMUv3 driver.
> >
> > This is on Github:
> > https://github.com/nicolinc/iommufd/commits/iommufd_veventq-v8
> > Paring QEMU branch for testing:
> > https://github.com/nicolinc/qemu/commits/wip/for_iommufd_veventq-v8
> 
> Thanks Nico
> 
> Tested-by: Zhangfei Gao <zhangfei.gao@...aro.org>
> 
> After rebase on your branch
> https://github.com/Linaro/linux-kernel-warpdrive/tree/iommufd_veventq-v8
> https://github.com/Linaro/qemu/tree/for_iommufd_veventq-v8
> 
> Tested with multi-device in guests, with io page faults happen.

Thanks for testing!

Nicolin