[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <201af18f-9978-4ced-ab3c-0deea06167a7@linux.intel.com>
Date: Mon, 26 Feb 2024 14:15:31 +0800
From: Baolu Lu <baolu.lu@...ux.intel.com>
To: Joerg Roedel <joro@...tes.org>, Will Deacon <will@...nel.org>,
Robin Murphy <robin.murphy@....com>, Jason Gunthorpe <jgg@...pe.ca>,
Kevin Tian <kevin.tian@...el.com>
Cc: baolu.lu@...ux.intel.com, Huang Jiaqing <jiaqing.huang@...el.com>,
Ethan Zhao <haifeng.zhao@...ux.intel.com>, iommu@...ts.linux.dev,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 0/2] iommu/vt-d: Introduce rbtree for probed devices
On 2/20/24 2:59 PM, Lu Baolu wrote:
> This is a follow-up to the discussion thread here:
>
> https://lore.kernel.org/linux-iommu/20240201193427.GQ50608@ziepe.ca/
>
> This proposes a per-IOMMU red-black tree for iommu probed devices. It
> benefits fault handling paths, where the VT-d hardware reports the
> Source ID of the related device, and software needs to retrieve the
> corresponding device pointer based on this ID.
>
> This is also available at github:
>
> https://github.com/LuBaolu/intel-iommu/commits/rbtree-for-device-info-v2
>
> Change log:
>
> v2:
> - Drop get/put_device() in device_rbtree_find();
> - Add a mutex to synchronize iopf report and device release paths.
>
> v1:https://lore.kernel.org/linux-iommu/20240215072249.4465-1-baolu.lu@linux.intel.com/
>
> Lu Baolu (2):
> iommu/vt-d: Use rbtree to track iommu probed devices
> iommu/vt-d: Use device rbtree in iopf reporting path
Above queued for v6.9.
Best regards,
baolu
Powered by blists - more mailing lists