From: Tina Zhang <tina.zhang@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Kevin Tian <kevin.tian@intel.com>,
Lu Baolu <baolu.lu@linux.intel.com>,
Michael Shavit <mshavit@google.com>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Tina Zhang <tina.zhang@intel.com>
Subject: [PATCH 1/5] iommu: Add mm_get_pasid() helper function
Date: Tue, 8 Aug 2023 15:49:40 +0800 [thread overview]
Message-ID: <20230808074944.7825-2-tina.zhang@intel.com> (raw)
In-Reply-To: <20230808074944.7825-1-tina.zhang@intel.com>
mm_get_pasid() is for getting mm pasid value.
The motivation is to replace mm->pasid with an iommu private data
structure that is introduced in a later patch.
Signed-off-by: Tina Zhang <tina.zhang@intel.com>
---
arch/x86/kernel/traps.c | 2 +-
include/linux/iommu.h | 8 ++++++++
2 files changed, 9 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/traps.c b/arch/x86/kernel/traps.c
index 4a817d20ce3b..6e259b11cd87 100644
--- a/arch/x86/kernel/traps.c
+++ b/arch/x86/kernel/traps.c
@@ -678,7 +678,7 @@ static bool try_fixup_enqcmd_gp(void)
if (!mm_valid_pasid(current->mm))
return false;
- pasid = current->mm->pasid;
+ pasid = mm_get_pasid(current->mm);
/*
* Did this thread already have its PASID activated?
diff --git a/include/linux/iommu.h b/include/linux/iommu.h
index d31642596675..30e4d1ca39b5 100644
--- a/include/linux/iommu.h
+++ b/include/linux/iommu.h
@@ -1180,6 +1180,10 @@ static inline bool mm_valid_pasid(struct mm_struct *mm)
{
return mm->pasid != IOMMU_PASID_INVALID;
}
+static inline u32 mm_get_pasid(struct mm_struct *mm)
+{
+ return mm->pasid;
+}
void mm_pasid_drop(struct mm_struct *mm);
struct iommu_sva *iommu_sva_bind_device(struct device *dev,
struct mm_struct *mm);
@@ -1202,6 +1206,10 @@ static inline u32 iommu_sva_get_pasid(struct iommu_sva *handle)
}
static inline void mm_pasid_init(struct mm_struct *mm) {}
static inline bool mm_valid_pasid(struct mm_struct *mm) { return false; }
+static inline u32 mm_get_pasid(struct mm_struct *mm)
+{
+ return IOMMU_PASID_INVALID;
+}
static inline void mm_pasid_drop(struct mm_struct *mm) {}
#endif /* CONFIG_IOMMU_SVA */
--
2.17.1
next prev parent reply other threads:[~2023-08-08 16:42 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 7:49 [PATCH 0/5] Share sva domains with all devices bound to a mm Tina Zhang
2023-08-08 7:49 ` Tina Zhang [this message]
2023-08-08 15:02 ` [PATCH 1/5] iommu: Add mm_get_pasid() helper function Jason Gunthorpe
2023-08-09 0:31 ` Baolu Lu
2023-08-09 9:47 ` Tian, Kevin
2023-08-09 12:31 ` Jason Gunthorpe
2023-08-08 7:49 ` [PATCH 2/5] iommu: Call helper function to get assigned pasid value Tina Zhang
2023-08-09 0:21 ` Baolu Lu
2023-08-09 9:49 ` Tian, Kevin
2023-08-09 10:58 ` Baolu Lu
2023-08-09 14:48 ` Jason Gunthorpe
2023-08-10 1:37 ` Baolu Lu
2023-08-10 16:30 ` Jason Gunthorpe
2023-08-09 12:35 ` Jason Gunthorpe
2023-08-10 7:52 ` Tian, Kevin
2023-08-10 16:36 ` Jason Gunthorpe
2023-08-11 3:18 ` Tian, Kevin
2023-08-08 7:49 ` [PATCH 3/5] mm: Add structure to keep sva information Tina Zhang
2023-08-08 7:49 ` [PATCH 4/5] iommu: Support mm PASID 1:n with sva domains Tina Zhang
2023-08-08 15:12 ` Jason Gunthorpe
2023-08-08 15:19 ` Jason Gunthorpe
2023-08-10 2:14 ` Tina Zhang
2023-08-08 7:49 ` [PATCH 5/5] mm: Deprecate pasid field Tina Zhang
2023-08-09 0:18 ` [PATCH 0/5] Share sva domains with all devices bound to a mm Baolu Lu
2023-08-09 9:44 ` Tian, Kevin
2023-08-09 10:51 ` Baolu Lu
2023-08-11 1:06 ` Tina Zhang
2023-08-09 14:46 ` Jason Gunthorpe
2023-08-10 1:23 ` Baolu Lu
2023-08-10 7:44 ` Tian, Kevin
2023-08-09 9:41 ` Tian, Kevin
2023-08-10 1:31 ` Tina Zhang
2023-08-10 7:49 ` Tian, Kevin
2023-08-10 16:27 ` Jason Gunthorpe
2023-08-11 1:12 ` Tina Zhang
2023-08-11 1:07 ` Tina Zhang
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=20230808074944.7825-2-tina.zhang@intel.com \
--to=tina.zhang@intel.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 \
/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
Powered by JetHome