kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Binbin Wu <binbin.wu@linux.intel.com>
To: kvm@vger.kernel.org
Cc: seanjc@google.com, pbonzini@redhat.com, chao.gao@intel.com,
	robert.hu@linux.intel.com, binbin.wu@linux.intel.com
Subject: [kvm-unit-tests v4 0/4] x86: Add test cases for LAM
Date: Thu,  4 May 2023 16:47:47 +0800	[thread overview]
Message-ID: <20230504084751.968-1-binbin.wu@linux.intel.com> (raw)

Intel Linear-address masking (LAM) [1], modifies the checking that is applied to
*64-bit* linear addresses, allowing software to use of the untranslated address
bits for metadata.

The patch series add test cases for KVM LAM:

Patch 1 makes change to allow setting of CR3 LAM bits in vmlaunch tests.
Patch 2~4 add test cases for LAM supervisor mode and user mode, including:
- For supervisor mode
  CR4.LAM_SUP toggle
  Memory/MMIO access with tagged pointer
  INVLPG
  INVPCID
  INVVPID (also used to cover VMX instruction VMExit path)
- For user mode
  CR3 LAM bits toggle 
  Memory/MMIO access with tagged pointer

[1] Intel ISE https://cdrdv2.intel.com/v1/dl/getContent/671368
    Chapter Linear Address Masking (LAM)

---
Changelog
v3 --> v4:
Remove an extra space in patch 1.
Remove an unnecessary local variable in patch 2.
Add some comments about the linear address used for LAM tests in patch 2 and patch 3.
Add a static assert to check the physical address range for LAM user mode tests in patch 3.
Remove the unnecessary identical mapping code in patch 3.
Move common definitions and helper function to header file in patch 2.
LAM test of INVVPID is tested only when individual-address invalidation is supported in patch 4.
Add reviewed-by from Chao Gao in patch 2~4.

v2 --> v3:
Simplify the implementation of set_metadata() (Suggested by Chao Gao)
Move definition of X86_FEATURE_LAM to patch 1.
Remove strcpy case and unify memory & MMIO address access using MOV instruction.
Some code cleanups.
Add reviewed-by from Chao Gao in patch 1. 

v1 --> v2:
Add cases to test INVLPG, INVPCID, INVVPID with LAM_SUP
Add cases to test LAM_{U48,U57}

Binbin Wu (3):
  x86: Allow setting of CR3 LAM bits if LAM supported
  x86: Add test cases for LAM_{U48,U57}
  x86: Add test case for INVVPID with LAM

Robert Hoo (1):
  x86: Add test case for LAM_SUP

 lib/x86/processor.h |  15 +++
 x86/Makefile.x86_64 |   1 +
 x86/lam.c           | 319 ++++++++++++++++++++++++++++++++++++++++++++
 x86/unittests.cfg   |  10 ++
 x86/vmx_tests.c     |  58 +++++++-
 5 files changed, 401 insertions(+), 2 deletions(-)
 create mode 100644 x86/lam.c


base-commit: 02d8befe99f8205d4caea402d8b0800354255681
-- 
2.25.1


             reply	other threads:[~2023-05-04  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-04  8:47 Binbin Wu [this message]
2023-05-04  8:47 ` [kvm-unit-tests v4 1/4] x86: Allow setting of CR3 LAM bits if LAM supported Binbin Wu
2023-05-04  8:47 ` [kvm-unit-tests v4 2/4] x86: Add test case for LAM_SUP Binbin Wu
2023-05-04  8:47 ` [kvm-unit-tests v4 3/4] x86: Add test cases for LAM_{U48,U57} Binbin Wu
2023-05-04  8:47 ` [kvm-unit-tests v4 4/4] x86: Add test case for INVVPID with LAM Binbin Wu
2023-05-09  1:38   ` Binbin Wu

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=20230504084751.968-1-binbin.wu@linux.intel.com \
    --to=binbin.wu@linux.intel.com \
    --cc=chao.gao@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=robert.hu@linux.intel.com \
    --cc=seanjc@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;
as well as URLs for NNTP newsgroup(s).