From: Baolu Lu <baolu.lu@linux.intel.com>
To: Joerg Roedel <joro@8bytes.org>, Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>
Cc: baolu.lu@linux.intel.com, Huang Jiaqing <jiaqing.huang@intel.com>,
Ethan Zhao <haifeng.zhao@linux.intel.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] iommu/vt-d: Introduce rbtree for probed devices
Date: Mon, 26 Feb 2024 14:15:31 +0800 [thread overview]
Message-ID: <201af18f-9978-4ced-ab3c-0deea06167a7@linux.intel.com> (raw)
In-Reply-To: <20240220065939.121116-1-baolu.lu@linux.intel.com>
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
prev parent reply other threads:[~2024-02-26 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 6:59 [PATCH v2 0/2] iommu/vt-d: Introduce rbtree for probed devices Lu Baolu
2024-02-20 6:59 ` [PATCH v2 1/2] iommu/vt-d: Use rbtree to track iommu " Lu Baolu
2024-02-20 6:59 ` [PATCH v2 2/2] iommu/vt-d: Use device rbtree in iopf reporting path Lu Baolu
2024-02-21 15:34 ` Jason Gunthorpe
2024-02-26 6:15 ` Baolu Lu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201af18f-9978-4ced-ab3c-0deea06167a7@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=haifeng.zhao@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jiaqing.huang@intel.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox