From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: joro@8bytes.org, alex.williamson@redhat.com
Cc: jacob.jun.pan@linux.intel.com, eric.auger@redhat.com,
ashok.raj@intel.com, yi.l.liu@linux.intel.com,
robdclark@gmail.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: [PATCH 0/4] iommu: Add device fault reporting API
Date: Thu, 23 May 2019 19:06:09 +0100 [thread overview]
Message-ID: <20190523180613.55049-1-jean-philippe.brucker@arm.com> (raw)
Allow device drivers and VFIO to get notifications on IOMMU translation
fault, and to handle recoverable faults (PCI PRI). These four patches
are relatively mature since they are required by three different series,
and have been under discussion for a while:
* Nested translation support for SMMUv3 [1].
* vSVA for VT-d [2].
* My generic host SVA implementation.
I reworked patch 4 according to previous discussions, and moved the page
response structure to UAPI. For the other patches I only fixed comments
and whitespaces. Please have a look and see if it works for you.
[1] [PATCH v7 00/23] SMMUv3 Nested Stage Setup
https://lore.kernel.org/lkml/20190408121911.24103-1-eric.auger@redhat.com/
[2] [PATCH v3 00/16] Shared virtual address IOMMU and VT-d support
https://lore.kernel.org/lkml/1556922737-76313-1-git-send-email-jacob.jun.pan@linux.intel.com/
Jacob Pan (3):
driver core: Add per device iommu param
iommu: Introduce device fault data
iommu: Introduce device fault report API
Jean-Philippe Brucker (1):
iommu: Add recoverable fault reporting
drivers/iommu/iommu.c | 218 +++++++++++++++++++++++++++++++++++++
include/linux/device.h | 3 +
include/linux/iommu.h | 91 ++++++++++++++++
include/uapi/linux/iommu.h | 152 ++++++++++++++++++++++++++
4 files changed, 464 insertions(+)
create mode 100644 include/uapi/linux/iommu.h
--
2.21.0
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
To: joro@8bytes.org, alex.williamson@redhat.com
Cc: yi.l.liu@linux.intel.com, ashok.raj@intel.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org
Subject: [PATCH 0/4] iommu: Add device fault reporting API
Date: Thu, 23 May 2019 19:06:09 +0100 [thread overview]
Message-ID: <20190523180613.55049-1-jean-philippe.brucker@arm.com> (raw)
Allow device drivers and VFIO to get notifications on IOMMU translation
fault, and to handle recoverable faults (PCI PRI). These four patches
are relatively mature since they are required by three different series,
and have been under discussion for a while:
* Nested translation support for SMMUv3 [1].
* vSVA for VT-d [2].
* My generic host SVA implementation.
I reworked patch 4 according to previous discussions, and moved the page
response structure to UAPI. For the other patches I only fixed comments
and whitespaces. Please have a look and see if it works for you.
[1] [PATCH v7 00/23] SMMUv3 Nested Stage Setup
https://lore.kernel.org/lkml/20190408121911.24103-1-eric.auger@redhat.com/
[2] [PATCH v3 00/16] Shared virtual address IOMMU and VT-d support
https://lore.kernel.org/lkml/1556922737-76313-1-git-send-email-jacob.jun.pan@linux.intel.com/
Jacob Pan (3):
driver core: Add per device iommu param
iommu: Introduce device fault data
iommu: Introduce device fault report API
Jean-Philippe Brucker (1):
iommu: Add recoverable fault reporting
drivers/iommu/iommu.c | 218 +++++++++++++++++++++++++++++++++++++
include/linux/device.h | 3 +
include/linux/iommu.h | 91 ++++++++++++++++
include/uapi/linux/iommu.h | 152 ++++++++++++++++++++++++++
4 files changed, 464 insertions(+)
create mode 100644 include/uapi/linux/iommu.h
--
2.21.0
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
next reply other threads:[~2019-05-23 18:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 18:06 Jean-Philippe Brucker [this message]
2019-05-23 18:06 ` [PATCH 0/4] iommu: Add device fault reporting API Jean-Philippe Brucker
2019-05-23 18:06 ` [PATCH 1/4] driver core: Add per device iommu param Jean-Philippe Brucker
2019-05-23 18:06 ` Jean-Philippe Brucker
2019-05-23 18:06 ` [PATCH 2/4] iommu: Introduce device fault data Jean-Philippe Brucker
2019-05-23 18:06 ` Jean-Philippe Brucker
2019-05-23 18:43 ` Robin Murphy
2019-05-23 18:43 ` Robin Murphy
2019-05-24 13:49 ` Jacob Pan
2019-05-24 13:49 ` Jacob Pan
2019-05-24 16:14 ` Jean-Philippe Brucker
2019-05-24 16:14 ` Jean-Philippe Brucker
2019-05-24 17:44 ` Jacob Pan
2019-05-24 17:44 ` Jacob Pan
2019-05-23 18:06 ` [PATCH 3/4] iommu: Introduce device fault report API Jean-Philippe Brucker
2019-05-23 18:06 ` Jean-Philippe Brucker
2019-05-23 18:56 ` Robin Murphy
2019-05-23 18:56 ` Robin Murphy
2019-05-24 18:00 ` Jacob Pan
2019-05-24 18:00 ` Jacob Pan
2019-05-31 13:37 ` Jean-Philippe Brucker
2019-05-31 13:37 ` Jean-Philippe Brucker
2019-05-23 18:06 ` [PATCH 4/4] iommu: Add recoverable fault reporting Jean-Philippe Brucker
2019-05-23 18:06 ` Jean-Philippe Brucker
2019-05-24 18:14 ` Jacob Pan
2019-05-24 18:14 ` Jacob Pan
2019-05-31 11:05 ` Jean-Philippe Brucker
2019-05-31 11:05 ` Jean-Philippe Brucker
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=20190523180613.55049-1-jean-philippe.brucker@arm.com \
--to=jean-philippe.brucker@arm.com \
--cc=alex.williamson@redhat.com \
--cc=ashok.raj@intel.com \
--cc=eric.auger@redhat.com \
--cc=iommu@lists.linux-foundation.org \
--cc=jacob.jun.pan@linux.intel.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=yi.l.liu@linux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.