RE: [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Nicolin Chen <nicolinc@xxxxxxxxxx>, "jgg@xxxxxxxxxx" <jgg@xxxxxxxxxx>, "corbet@xxxxxxx" <corbet@xxxxxxx>, "will@xxxxxxxxxx" <will@xxxxxxxxxx>
Subject: RE: [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Tue, 18 Feb 2025 05:21:29 +0000
Accept-language: en-US
Cc: "joro@xxxxxxxxxx" <joro@xxxxxxxxxx>, "suravee.suthikulpanit@xxxxxxx" <suravee.suthikulpanit@xxxxxxx>, "robin.murphy@xxxxxxx" <robin.murphy@xxxxxxx>, "dwmw2@xxxxxxxxxxxxx" <dwmw2@xxxxxxxxxxxxx>, "baolu.lu@xxxxxxxxxxxxxxx" <baolu.lu@xxxxxxxxxxxxxxx>, "shuah@xxxxxxxxxx" <shuah@xxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, "iommu@xxxxxxxxxxxxxxx" <iommu@xxxxxxxxxxxxxxx>, "linux-arm-kernel@xxxxxxxxxxxxxxxxxxx" <linux-arm-kernel@xxxxxxxxxxxxxxxxxxx>, "linux-kselftest@xxxxxxxxxxxxxxx" <linux-kselftest@xxxxxxxxxxxxxxx>, "linux-doc@xxxxxxxxxxxxxxx" <linux-doc@xxxxxxxxxxxxxxx>, "eric.auger@xxxxxxxxxx" <eric.auger@xxxxxxxxxx>, "jean-philippe@xxxxxxxxxx" <jean-philippe@xxxxxxxxxx>, "mdf@xxxxxxxxxx" <mdf@xxxxxxxxxx>, "mshavit@xxxxxxxxxx" <mshavit@xxxxxxxxxx>, "shameerali.kolothum.thodi@xxxxxxxxxx" <shameerali.kolothum.thodi@xxxxxxxxxx>, "smostafa@xxxxxxxxxx" <smostafa@xxxxxxxxxx>, "ddutile@xxxxxxxxxx" <ddutile@xxxxxxxxxx>, "Liu, Yi L" <yi.l.liu@xxxxxxxxx>, "patches@xxxxxxxxxxxxxxx" <patches@xxxxxxxxxxxxxxx>
In-reply-to: <b71a5b132e8ba771998c5b810675f10b100d4ff3.1737754129.git.nicolinc@nvidia.com>
Thread-index: AQHbbsCBPjGt+w3jJEeCRiZ6nDct0bNMrFUg
Thread-topic: [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU

> From: Nicolin Chen <nicolinc@xxxxxxxxxx>
> Sent: Saturday, January 25, 2025 8:31 AM
> 
> Aside from the IOPF framework, iommufd provides an additional pathway to
> report hardware events, via the vEVENTQ of vIOMMU infrastructure.
> 
> Define an iommu_vevent_arm_smmuv3 uAPI structure, and report stage-1
> events
> in the threaded IRQ handler.
> 
> Signed-off-by: Nicolin Chen <nicolinc@xxxxxxxxxx>

Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx>

References:
- [PATCH v6 00/14] iommufd: Add vIOMMU infrastructure (Part-3: vEVENTQ)
  - From: Nicolin Chen
- [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU
  - From: Nicolin Chen

Prev by Date: RE: [PATCH v6 10/14] iommufd/selftest: Add IOMMU_VEVENTQ_ALLOC test coverage
Next by Date: RE: [PATCH v6 14/14] iommu/arm-smmu-v3: Set MEV bit in nested STE for DoS mitigations
Previous by thread: [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU
Next by thread: Re: [PATCH v6 13/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU
Index(es):
- Date
- Thread

[Index of Archives] [Linux Wireless] [Linux Kernel] [ATH6KL] [Linux Bluetooth] [Linux Netdev] [Kernel Newbies] [Share Photos] [IDE] [Security] [Git] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux ATA RAID] [Samba] [Device Mapper]