From: Nicolin Chen <nicolinc@nvidia.com>
To: <jgg@nvidia.com>, <kevin.tian@intel.com>
Cc: <baolu.lu@linux.intel.com>, <iommu@lists.linux.dev>,
<linux-kernel@vger.kernel.org>, <joro@8bytes.org>,
<will@kernel.org>, <robin.murphy@arm.com>
Subject: [PATCH rc 0/2] iommufd/fault: Two bug fixes prior to vEVENTQ
Date: Tue, 14 Jan 2025 15:28:43 -0800 [thread overview]
Message-ID: <cover.1736894696.git.nicolinc@nvidia.com> (raw)
It is too late to get the vEVENTQ series merged in this cycle, while some
bug fixes for the fault.c file can go in first. These fix two small bugs.
I will send vEVENTQ v6 later to get reviewed. And hopefully that can get
merged in the early weeks of the next cycle.
Thanks
Nicolin
Nicolin Chen (2):
iommufd/fault: Destroy response and mutex in iommufd_fault_destroy()
iommufd/fault: Use a separate spinlock to protect fault->deliver list
drivers/iommu/iommufd/iommufd_private.h | 26 +++++++++++++
drivers/iommu/iommufd/fault.c | 51 ++++++++++++++++---------
2 files changed, 58 insertions(+), 19 deletions(-)
--
2.43.0
next reply other threads:[~2025-01-14 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 23:28 Nicolin Chen [this message]
2025-01-14 23:28 ` [PATCH rc 1/2] iommufd/fault: Destroy response and mutex in iommufd_fault_destroy() Nicolin Chen
2025-01-15 0:54 ` Jason Gunthorpe
2025-01-15 5:17 ` Tian, Kevin
2025-01-15 5:21 ` Baolu Lu
2025-01-14 23:28 ` [PATCH rc 2/2] iommufd/fault: Use a separate spinlock to protect fault->deliver list Nicolin Chen
2025-01-15 5:24 ` Tian, Kevin
2025-01-15 5:40 ` Nicolin Chen
2025-01-15 5:24 ` Baolu Lu
2025-01-15 5:45 ` Nicolin Chen
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=cover.1736894696.git.nicolinc@nvidia.com \
--to=nicolinc@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.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