From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
kvm@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
Cornelia Huck <cohuck@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>,
iommu@lists.linux-foundation.org,
Robin Murphy <robin.murphy@arm.com>,
Will Deacon <will@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 0/4] Make the iommu driver no-snoop block feature consistent
Date: Thu, 28 Apr 2022 10:56:33 +0200 [thread overview]
Message-ID: <YmpWwbcrl5OntB+g@8bytes.org> (raw)
In-Reply-To: <0-v3-2cf356649677+a32-intel_no_snoop_jgg@nvidia.com>
On Mon, Apr 11, 2022 at 12:16:04PM -0300, Jason Gunthorpe wrote:
> Jason Gunthorpe (4):
> iommu: Introduce the domain op enforce_cache_coherency()
> vfio: Move the Intel no-snoop control off of IOMMU_CACHE
> iommu: Redefine IOMMU_CAP_CACHE_COHERENCY as the cap flag for
> IOMMU_CACHE
> vfio: Require that devices support DMA cache coherence
>
> drivers/iommu/amd/iommu.c | 7 +++++++
> drivers/iommu/intel/iommu.c | 17 +++++++++++++----
> drivers/vfio/vfio.c | 7 +++++++
> drivers/vfio/vfio_iommu_type1.c | 30 +++++++++++++++++++-----------
> include/linux/intel-iommu.h | 2 +-
> include/linux/iommu.h | 7 +++++--
> 6 files changed, 52 insertions(+), 18 deletions(-)
Applied to core branch, thanks everyone.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
David Woodhouse <dwmw2@infradead.org>,
iommu@lists.linux-foundation.org, kvm@vger.kernel.org,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Will Deacon <will@kernel.org>,
Alex Williamson <alex.williamson@redhat.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Christoph Hellwig <hch@lst.de>,
"Tian, Kevin" <kevin.tian@intel.com>,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [PATCH v3 0/4] Make the iommu driver no-snoop block feature consistent
Date: Thu, 28 Apr 2022 10:56:33 +0200 [thread overview]
Message-ID: <YmpWwbcrl5OntB+g@8bytes.org> (raw)
In-Reply-To: <0-v3-2cf356649677+a32-intel_no_snoop_jgg@nvidia.com>
On Mon, Apr 11, 2022 at 12:16:04PM -0300, Jason Gunthorpe wrote:
> Jason Gunthorpe (4):
> iommu: Introduce the domain op enforce_cache_coherency()
> vfio: Move the Intel no-snoop control off of IOMMU_CACHE
> iommu: Redefine IOMMU_CAP_CACHE_COHERENCY as the cap flag for
> IOMMU_CACHE
> vfio: Require that devices support DMA cache coherence
>
> drivers/iommu/amd/iommu.c | 7 +++++++
> drivers/iommu/intel/iommu.c | 17 +++++++++++++----
> drivers/vfio/vfio.c | 7 +++++++
> drivers/vfio/vfio_iommu_type1.c | 30 +++++++++++++++++++-----------
> include/linux/intel-iommu.h | 2 +-
> include/linux/iommu.h | 7 +++++--
> 6 files changed, 52 insertions(+), 18 deletions(-)
Applied to core branch, thanks everyone.
next prev parent reply other threads:[~2022-04-28 8:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:16 [PATCH v3 0/4] Make the iommu driver no-snoop block feature consistent Jason Gunthorpe via iommu
2022-04-11 15:16 ` Jason Gunthorpe
2022-04-11 15:16 ` [PATCH v3 1/4] iommu: Introduce the domain op enforce_cache_coherency() Jason Gunthorpe via iommu
2022-04-11 15:16 ` Jason Gunthorpe
2022-04-11 15:16 ` [PATCH v3 2/4] vfio: Move the Intel no-snoop control off of IOMMU_CACHE Jason Gunthorpe via iommu
2022-04-11 15:16 ` Jason Gunthorpe
2022-04-11 15:16 ` [PATCH v3 3/4] iommu: Redefine IOMMU_CAP_CACHE_COHERENCY as the cap flag for IOMMU_CACHE Jason Gunthorpe via iommu
2022-04-11 15:16 ` Jason Gunthorpe
2022-04-11 15:16 ` [PATCH v3 4/4] vfio: Require that devices support DMA cache coherence Jason Gunthorpe via iommu
2022-04-11 15:16 ` Jason Gunthorpe
2022-07-04 13:21 ` chenxiang (M) via iommu
2022-07-04 13:21 ` chenxiang (M)
2022-07-04 13:27 ` Jason Gunthorpe via iommu
2022-07-04 13:27 ` Jason Gunthorpe
2022-04-28 8:56 ` Joerg Roedel [this message]
2022-04-28 8:56 ` [PATCH v3 0/4] Make the iommu driver no-snoop block feature consistent Joerg Roedel
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=YmpWwbcrl5OntB+g@8bytes.org \
--to=joro@8bytes.org \
--cc=alex.williamson@redhat.com \
--cc=cohuck@redhat.com \
--cc=dwmw2@infradead.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=jgg@nvidia.com \
--cc=kevin.tian@intel.com \
--cc=kvm@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 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.