linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
To: kirill.shutemov@linux.intel.com
Cc: ak@linux.intel.com, andreyknvl@gmail.com,
	dave.hansen@linux.intel.com, dvyukov@google.com,
	glider@google.com, hjl.tools@gmail.com, kcc@google.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	luto@kernel.org, peterz@infradead.org,
	rick.p.edgecombe@intel.com, ryabinin.a.a@gmail.com,
	tarasmadan@google.com, x86@kernel.org
Subject: [PATCHv6.1 06/11] x86/mm: Provide arch_prctl() interface for LAM
Date: Tue, 16 Aug 2022 03:10:21 +0300	[thread overview]
Message-ID: <20220816001021.9476-1-kirill.shutemov@linux.intel.com> (raw)
In-Reply-To: <20220815041803.17954-7-kirill.shutemov@linux.intel.com>

Add a couple of arch_prctl() handles:

 - ARCH_ENABLE_TAGGED_ADDR enabled LAM. The argument is required number
   of tag bits. It is rounded up to the nearest LAM mode that can
   provide it. For now only LAM_U57 is supported, with 6 tag bits.

 - ARCH_GET_UNTAG_MASK returns untag mask. It can indicates where tag
   bits located in the address.

 - ARCH_GET_MAX_TAG_BITS returns the maximum tag bits user can request.
   Zero if LAM is not supported.

Signed-off-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
---
 v6.1:
  - Drop redundant smb_mb() in prctl_enable_tagged_addr();
---
 arch/x86/include/uapi/asm/prctl.h |  4 ++
 arch/x86/kernel/process_64.c      | 62 ++++++++++++++++++++++++++++++-
 2 files changed, 65 insertions(+), 1 deletion(-)

diff --git a/arch/x86/include/uapi/asm/prctl.h b/arch/x86/include/uapi/asm/prctl.h
index 500b96e71f18..a31e27b95b19 100644
--- a/arch/x86/include/uapi/asm/prctl.h
+++ b/arch/x86/include/uapi/asm/prctl.h
@@ -20,4 +20,8 @@
 #define ARCH_MAP_VDSO_32		0x2002
 #define ARCH_MAP_VDSO_64		0x2003
 
+#define ARCH_GET_UNTAG_MASK		0x4001
+#define ARCH_ENABLE_TAGGED_ADDR		0x4002
+#define ARCH_GET_MAX_TAG_BITS		0x4003
+
 #endif /* _ASM_X86_PRCTL_H */
diff --git a/arch/x86/kernel/process_64.c b/arch/x86/kernel/process_64.c
index 1962008fe743..28b9657ce2d0 100644
--- a/arch/x86/kernel/process_64.c
+++ b/arch/x86/kernel/process_64.c
@@ -742,6 +742,57 @@ static long prctl_map_vdso(const struct vdso_image *image, unsigned long addr)
 }
 #endif
 
+static void enable_lam_func(void *mm)
+{
+	struct mm_struct *loaded_mm = this_cpu_read(cpu_tlbstate.loaded_mm);
+	unsigned long lam_mask;
+	unsigned long cr3;
+
+	if (loaded_mm != mm)
+		return;
+
+	lam_mask = READ_ONCE(loaded_mm->context.lam_cr3_mask);
+
+	/* Update CR3 to get LAM active on the CPU */
+	cr3 = __read_cr3();
+	cr3 &= ~(X86_CR3_LAM_U48 | X86_CR3_LAM_U57);
+	cr3 |= lam_mask;
+	write_cr3(cr3);
+	set_tlbstate_cr3_lam_mask(lam_mask);
+}
+
+static int prctl_enable_tagged_addr(struct mm_struct *mm, unsigned long nr_bits)
+{
+	int ret = 0;
+
+	if (!cpu_feature_enabled(X86_FEATURE_LAM))
+		return -ENODEV;
+
+	mutex_lock(&mm->context.lock);
+
+	/* Already enabled? */
+	if (mm->context.lam_cr3_mask) {
+		ret = -EBUSY;
+		goto out;
+	}
+
+	if (!nr_bits) {
+		ret = -EINVAL;
+		goto out;
+	} else if (nr_bits <= 6) {
+		mm->context.lam_cr3_mask = X86_CR3_LAM_U57;
+		mm->context.untag_mask =  ~GENMASK(62, 57);
+	} else {
+		ret = -EINVAL;
+		goto out;
+	}
+
+	on_each_cpu_mask(mm_cpumask(mm), enable_lam_func, mm, true);
+out:
+	mutex_unlock(&mm->context.lock);
+	return ret;
+}
+
 long do_arch_prctl_64(struct task_struct *task, int option, unsigned long arg2)
 {
 	int ret = 0;
@@ -829,7 +880,16 @@ long do_arch_prctl_64(struct task_struct *task, int option, unsigned long arg2)
 	case ARCH_MAP_VDSO_64:
 		return prctl_map_vdso(&vdso_image_64, arg2);
 #endif
-
+	case ARCH_GET_UNTAG_MASK:
+		return put_user(task->mm->context.untag_mask,
+				(unsigned long __user *)arg2);
+	case ARCH_ENABLE_TAGGED_ADDR:
+		return prctl_enable_tagged_addr(task->mm, arg2);
+	case ARCH_GET_MAX_TAG_BITS:
+		if (!cpu_feature_enabled(X86_FEATURE_LAM))
+			return put_user(0, (unsigned long __user *)arg2);
+		else
+			return put_user(6, (unsigned long __user *)arg2);
 	default:
 		ret = -EINVAL;
 		break;
-- 
2.35.1



  parent reply	other threads:[~2022-08-16  0:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15  4:17 [PATCHv6 00/11] Linear Address Masking enabling Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 01/11] x86/mm: Fix CR3_ADDR_MASK Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 02/11] x86: CPUID and CR3/CR4 flags for Linear Address Masking Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 03/11] mm: Pass down mm_struct to untagged_addr() Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 04/11] x86/mm: Handle LAM on context switch Kirill A. Shutemov
2022-08-15 13:33   ` Peter Zijlstra
2022-08-15 13:42   ` Peter Zijlstra
2022-08-15 17:37     ` Kirill A. Shutemov
2022-08-15 18:02       ` Peter Zijlstra
2022-08-16  0:07   ` [PATCHv6.1 " Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 05/11] x86/uaccess: Provide untagged_addr() and remove tags before address check Kirill A. Shutemov
2022-08-15  4:17 ` [PATCHv6 06/11] x86/mm: Provide arch_prctl() interface for LAM Kirill A. Shutemov
2022-08-15 13:37   ` Peter Zijlstra
2022-08-15 17:52     ` Kirill A. Shutemov
2022-08-16  0:10   ` Kirill A. Shutemov [this message]
2022-08-22  9:32   ` Alexander Potapenko
2022-08-23 13:16     ` Alexander Potapenko
2022-08-15  4:17 ` [PATCHv6 07/11] x86: Expose untagging mask in /proc/$PID/arch_status Kirill A. Shutemov
2022-08-15  4:18 ` [PATCHv6 08/11] selftests/x86/lam: Add malloc and tag-bits test cases for linear-address masking Kirill A. Shutemov
2022-08-19  5:17   ` Hu, Robert
2022-08-22  5:21     ` Zhang, Weihong
2022-08-15  4:18 ` [PATCHv6 09/11] selftests/x86/lam: Add mmap and SYSCALL " Kirill A. Shutemov
2022-08-19  8:15   ` Hu, Robert
2022-08-22  8:47     ` Zhang, Weihong
2022-08-15  4:18 ` [PATCHv6 10/11] selftests/x86/lam: Add io_uring " Kirill A. Shutemov
2022-08-15  4:18 ` [PATCHv6 11/11] selftests/x86/lam: Add inherit " Kirill A. Shutemov
2022-08-15 13:43 ` [PATCHv6 00/11] Linear Address Masking enabling Peter Zijlstra
2022-08-23  8:58   ` Alexander Potapenko

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=20220816001021.9476-1-kirill.shutemov@linux.intel.com \
    --to=kirill.shutemov@linux.intel.com \
    --cc=ak@linux.intel.com \
    --cc=andreyknvl@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dvyukov@google.com \
    --cc=glider@google.com \
    --cc=hjl.tools@gmail.com \
    --cc=kcc@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rick.p.edgecombe@intel.com \
    --cc=ryabinin.a.a@gmail.com \
    --cc=tarasmadan@google.com \
    --cc=x86@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