From: Nicolin Chen <nicolinc@nvidia.com>
To: Tina Zhang <tina.zhang@intel.com>
Cc: <iommu@lists.linux.dev>, <linux-kernel@vger.kernel.org>,
David Woodhouse <dwmw2@infradead.org>,
Lu Baolu <baolu.lu@linux.intel.com>,
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>,
Michael Shavit <mshavit@google.com>,
Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: [PATCH v8 0/5] Share sva domains with all devices bound to a mm
Date: Mon, 16 Oct 2023 19:19:27 -0700 [thread overview]
Message-ID: <ZS3vLxikjXj7gDlI@Asurada-Nvidia> (raw)
In-Reply-To: <20231017004802.109618-1-tina.zhang@intel.com>
On Tue, Oct 17, 2023 at 08:47:57AM +0800, Tina Zhang wrote:
> v8:
> - CC more people
> - CC iommu@lists.linux.dev mailing list.
> When sending version 7, some issue happened in my CC list and that caused
> version 7 wasn't sent to iommu@lists.linux.dev.
> - Rebase to v6.6-rc6 and make a few format changes.
Tried Sanity with SMMUv3, though there is a merge conflict
against Michael's SMMU series:
https://lore.kernel.org/linux-iommu/169712689838.645382.14628592932614139960.b4-ty@kernel.org/
Tested-by: Nicolin Chen <nicolinc@nvidia.com>
next prev parent reply other threads:[~2023-10-17 2:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 0:47 Tina Zhang
2023-10-17 0:47 ` [PATCH v8 1/5] iommu/vt-d: Remove mm->pasid in intel_sva_bind_mm() Tina Zhang
2023-10-17 0:47 ` [PATCH v8 2/5] iommu: Add mm_get_enqcmd_pasid() helper function Tina Zhang
2023-10-17 0:48 ` [PATCH v8 3/5] mm: Add structure to keep sva information Tina Zhang
2023-10-17 0:48 ` [PATCH v8 4/5] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-10-17 0:48 ` [PATCH v8 5/5] mm: Deprecate pasid field Tina Zhang
2023-10-17 2:19 ` Nicolin Chen [this message]
2023-10-17 16:41 ` [PATCH v8 0/5] Share sva domains with all devices bound to a mm Jason Gunthorpe
2023-10-18 2:13 ` Baolu Lu
2023-10-18 4:43 ` Zhang, Tina
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=ZS3vLxikjXj7gDlI@Asurada-Nvidia \
--to=nicolinc@nvidia.com \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=robin.murphy@arm.com \
--cc=tina.zhang@intel.com \
--cc=vasant.hegde@amd.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
all inboxes | Powered by JetHome®