From: Vasant Hegde <vasant.hegde@amd.com>
To: Tina Zhang <tina.zhang@intel.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Kevin Tian <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>
Cc: Michael Shavit <mshavit@google.com>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 6/6] mm: Deprecate pasid field
Date: Tue, 5 Sep 2023 10:29:37 +0530 [thread overview]
Message-ID: <8be32518-ce53-744a-9fe5-9f2a33095c18@amd.com> (raw)
In-Reply-To: <20230905000930.24515-7-tina.zhang@intel.com>
On 9/5/2023 5:39 AM, Tina Zhang wrote:
> Drop the pasid field, as all the information needed for sva domain
> management has been moved to the newly added iommu_mm field.
>
> Reviewed-by: Lu Baolu <baolu.lu@linux.intel.com>
> Signed-off-by: Tina Zhang <tina.zhang@intel.com>
Looks good to me.
Reviewed-by: Vasant Hegde <vasant.hegde@amd.com>
-Vasant
> ---
> include/linux/mm_types.h | 1 -
> mm/init-mm.c | 3 ---
> 2 files changed, 4 deletions(-)
>
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index b486f521afee..fb0e4416d9d7 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -808,7 +808,6 @@ struct mm_struct {
> struct work_struct async_put_work;
>
> #ifdef CONFIG_IOMMU_SVA
> - u32 pasid;
> struct iommu_mm_data *iommu_mm;
> #endif
> #ifdef CONFIG_KSM
> diff --git a/mm/init-mm.c b/mm/init-mm.c
> index efa97b57acfd..69719291463e 100644
> --- a/mm/init-mm.c
> +++ b/mm/init-mm.c
> @@ -42,9 +42,6 @@ struct mm_struct init_mm = {
> #endif
> .user_ns = &init_user_ns,
> .cpu_bitmap = CPU_BITS_NONE,
> -#ifdef CONFIG_IOMMU_SVA
> - .pasid = IOMMU_PASID_INVALID,
> -#endif
> INIT_MM_CONTEXT(init_mm)
> };
>
prev parent reply other threads:[~2023-09-05 16:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-05 0:09 [PATCH v3 0/6] Share sva domains with all devices bound to a mm Tina Zhang
2023-09-05 0:09 ` [PATCH v3 1/6] iommu: Add mm_get_enqcmd_pasid() helper function Tina Zhang
2023-09-05 0:09 ` [PATCH v3 2/6] iommu/vt-d: Remove mm->pasid in intel_sva_bind_mm() Tina Zhang
2023-09-05 0:09 ` [PATCH v3 3/6] iommu: Introduce mm_get_pasid() helper function Tina Zhang
2023-09-05 0:09 ` [PATCH v3 4/6] mm: Add structure to keep sva information Tina Zhang
2023-09-05 4:58 ` Vasant Hegde
2023-09-05 0:09 ` [PATCH v3 5/6] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-09-05 4:56 ` Vasant Hegde
2023-09-05 0:09 ` [PATCH v3 6/6] mm: Deprecate pasid field Tina Zhang
2023-09-05 4:59 ` Vasant Hegde [this message]
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=8be32518-ce53-744a-9fe5-9f2a33095c18@amd.com \
--to=vasant.hegde@amd.com \
--cc=baolu.lu@linux.intel.com \
--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=tina.zhang@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
all inboxes | Powered by JetHome®