From: Joerg Roedel <joro@8bytes.org>
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>,
Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Nicolin Chen <nicolinc@nvidia.com>,
Michael Shavit <mshavit@google.com>,
Vasant Hegde <vasant.hegde@amd.com>
Subject: Re: [PATCH v9 0/5] Share sva domains with all devices bound to a mm
Date: Thu, 26 Oct 2023 09:24:40 +0200 [thread overview]
Message-ID: <ZToUOKSqqI6Bh_03@8bytes.org> (raw)
In-Reply-To: <20231018050640.24936-1-tina.zhang@intel.com>
Hi Tina,
On Wed, Oct 18, 2023 at 01:06:35PM +0800, Tina Zhang wrote:
> Tina Zhang (5):
> iommu/vt-d: Remove mm->pasid in intel_sva_bind_mm()
> iommu: Add mm_get_enqcmd_pasid() helper function
> mm: Add structure to keep sva information
> iommu: Support mm PASID 1:n with sva domains
> mm: Deprecate pasid field
Thanks for doing this, it all looks reasonable to me. But there is one
thing missing which needs to be done before we can move forward with
this.
There was a discussion about the Kconfig symbol naming used in
mm_struct. Please see the discussion here:
https://lore.kernel.org/all/CAHk-=wgUiAtiszwseM1p2fCJ+sC4XWQ+YN4TanFhUgvUqjr9Xw@mail.gmail.com/
Please update this patch-set to solve this and I will take the series.
Regards,
Joerg
next prev parent reply other threads:[~2023-10-26 7:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 5:06 [PATCH v9 0/5] Share sva domains with all devices bound to a mm Tina Zhang
2023-10-18 5:06 ` [PATCH v9 1/5] iommu/vt-d: Remove mm->pasid in intel_sva_bind_mm() Tina Zhang
2023-10-18 5:06 ` [PATCH v9 2/5] iommu: Add mm_get_enqcmd_pasid() helper function Tina Zhang
2023-10-18 5:06 ` [PATCH v9 3/5] mm: Add structure to keep sva information Tina Zhang
2023-10-18 5:06 ` [PATCH v9 4/5] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-10-18 5:06 ` [PATCH v9 5/5] mm: Deprecate pasid field Tina Zhang
2023-10-25 12:30 ` [PATCH v9 0/5] Share sva domains with all devices bound to a mm Jason Gunthorpe
2023-10-26 7:24 ` Joerg Roedel [this message]
2023-10-26 12:20 ` Jason Gunthorpe
2023-10-26 13:50 ` Jason Gunthorpe
2023-10-27 0:10 ` 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=ZToUOKSqqI6Bh_03@8bytes.org \
--to=joro@8bytes.org \
--cc=baolu.lu@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mshavit@google.com \
--cc=nicolinc@nvidia.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