Re: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper

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

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Subject: Re: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
From: Jason Gunthorpe <jgg@xxxxxxxxxx>
Date: Fri, 21 Feb 2025 09:39:07 -0400
Cc: Nicolin Chen <nicolinc@xxxxxxxxxx>, "corbet@xxxxxxx" <corbet@xxxxxxx>, "will@xxxxxxxxxx" <will@xxxxxxxxxx>, "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: <BN9PR11MB5276DCBA230A17136BEDB7FE8CC72@BN9PR11MB5276.namprd11.prod.outlook.com>
References: <cover.1737754129.git.nicolinc@nvidia.com> <3d952137a7935608f9cc6b05bd561a58a0c5da16.1737754129.git.nicolinc@nvidia.com> <20250218153541.GD4099685@nvidia.com> <BN9PR11MB52766CE9C579D3EE1CE1A7058CC52@BN9PR11MB5276.namprd11.prod.outlook.com> <Z7ebqtJUwzgOIeSC@Asurada-Nvidia> <BN9PR11MB5276DCBA230A17136BEDB7FE8CC72@BN9PR11MB5276.namprd11.prod.outlook.com>

On Fri, Feb 21, 2025 at 04:27:32AM +0000, Tian, Kevin wrote:
> With that in mind we don't need provide reason for the static node,
> and IOMMU_EVENTQ_FLAG_LOST_EVENTS sounds closer to the
> real intention.

I also like lost events - it is simple and to the point

Jason

References:
- [PATCH v6 00/14] iommufd: Add vIOMMU infrastructure (Part-3: vEVENTQ)
  - From: Nicolin Chen
- [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
  - From: Nicolin Chen
- Re: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
  - From: Jason Gunthorpe
- RE: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
  - From: Tian, Kevin
- Re: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
  - From: Nicolin Chen
- RE: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
  - From: Tian, Kevin

Prev by Date: Re: [PATCH net-next v5 1/2] net, treewide: define and use MAC_ADDR_STR_LEN
Next by Date: [PATCH] fixup define name
Previous by thread: RE: [PATCH v6 07/14] iommufd/viommu: Add iommufd_viommu_report_event helper
Next by thread: [PATCH v6 08/14] iommufd/selftest: Require vdev_id when attaching to a nested domain
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Linux FS] [Yosemite Forum] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper] [Linux Resources]