From: Baolu Lu <baolu.lu@linux.intel.com>
To: Nicolin Chen <nicolinc@nvidia.com>,
jgg@nvidia.com, kevin.tian@intel.com, corbet@lwn.net,
will@kernel.org
Cc: joro@8bytes.org, suravee.suthikulpanit@amd.com,
robin.murphy@arm.com, dwmw2@infradead.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-doc@vger.kernel.org,
eric.auger@redhat.com, jean-philippe@linaro.org, mdf@kernel.org,
mshavit@google.com, shameerali.kolothum.thodi@huawei.com,
smostafa@google.com, ddutile@redhat.com, yi.l.liu@intel.com,
patches@lists.linux.dev
Subject: Re: [PATCH v4 08/14] iommufd/viommu: Add iommufd_viommu_report_event helper
Date: Mon, 6 Jan 2025 10:51:27 +0800 [thread overview]
Message-ID: <d65e1a7f-8b3d-4d3b-bcd0-38ef02791ca7@linux.intel.com> (raw)
In-Reply-To: <cbf90c55a1b8fb7c9d0619d0c12362e699d2b642.1735933254.git.nicolinc@nvidia.com>
On 1/4/25 03:43, Nicolin Chen wrote:
> Similar to iommu_report_device_fault, this allows IOMMU drivers to report
> vIOMMU events from threaded IRQ handlers to user space hypervisors.
>
> Signed-off-by: Nicolin Chen<nicolinc@nvidia.com>
> ---
> include/linux/iommufd.h | 11 ++++++++++
> drivers/iommu/iommufd/driver.c | 40 ++++++++++++++++++++++++++++++++++
> 2 files changed, 51 insertions(+)
Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
next prev parent reply other threads:[~2025-01-06 3:02 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 19:43 [PATCH v4 00/14] iommufd: Add vIOMMU infrastructure (Part-3: vEVENTQ) Nicolin Chen
2025-01-03 19:43 ` [PATCH v4 01/14] iommufd: Keep IOCTL list in an alphabetical order Nicolin Chen
2025-01-06 2:47 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 02/14] iommufd/fault: Add an iommufd_fault_init() helper Nicolin Chen
2025-01-06 2:48 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 03/14] iommufd/fault: Move iommufd_fault_iopf_handler() to header Nicolin Chen
2025-01-06 2:48 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 04/14] iommufd: Abstract an iommufd_eventq from iommufd_fault Nicolin Chen
2025-01-06 2:49 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 05/14] iommufd: Rename fault.c to eventq.c Nicolin Chen
2025-01-06 2:49 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 06/14] iommufd: Add IOMMUFD_OBJ_VEVENTQ and IOMMUFD_CMD_VEVENTQ_ALLOC Nicolin Chen
2025-01-06 2:50 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 07/14] iommufd/viommu: Add iommufd_viommu_get_vdev_id helper Nicolin Chen
2025-01-06 2:50 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 08/14] iommufd/viommu: Add iommufd_viommu_report_event helper Nicolin Chen
2025-01-06 2:51 ` Baolu Lu [this message]
2025-01-03 19:43 ` [PATCH v4 09/14] iommufd/selftest: Require vdev_id when attaching to a nested domain Nicolin Chen
2025-01-03 19:43 ` [PATCH v4 10/14] iommufd/selftest: Add IOMMU_TEST_OP_TRIGGER_VEVENT for vEVENTQ coverage Nicolin Chen
2025-01-03 19:43 ` [PATCH v4 11/14] iommufd/selftest: Add IOMMU_VEVENTQ_ALLOC test coverage Nicolin Chen
2025-01-03 19:43 ` [PATCH v4 12/14] Documentation: userspace-api: iommufd: Update FAULT and VEVENTQ Nicolin Chen
2025-01-06 2:51 ` Baolu Lu
2025-01-03 19:43 ` [PATCH v4 13/14] iommu/arm-smmu-v3: Introduce struct arm_smmu_vmaster Nicolin Chen
2025-01-03 19:43 ` [PATCH v4 14/14] iommu/arm-smmu-v3: Report events that belong to devices attached to vIOMMU Nicolin Chen
2025-01-06 3:01 ` Baolu Lu
2025-01-06 18:46 ` Nicolin Chen
2025-01-07 4:36 ` Nicolin Chen
2025-01-07 5:33 ` Nicolin Chen
2025-01-07 5:54 ` Baolu Lu
2025-01-07 6:00 ` Nicolin Chen
2025-01-07 6:27 ` Baolu Lu
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=d65e1a7f-8b3d-4d3b-bcd0-38ef02791ca7@linux.intel.com \
--to=baolu.lu@linux.intel.com \
--cc=corbet@lwn.net \
--cc=ddutile@redhat.com \
--cc=dwmw2@infradead.org \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.com \
--cc=patches@lists.linux.dev \
--cc=robin.murphy@arm.com \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shuah@kernel.org \
--cc=smostafa@google.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=will@kernel.org \
--cc=yi.l.liu@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).