From: Sean Christopherson <seanjc@google.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, chao.gao@intel.com,
robert.hu@linux.intel.com
Subject: Re: [kvm-unit-tests PATCH v6 4/4] x86: Add test case for INVVPID with LAM
Date: Wed, 5 Jun 2024 11:57:03 -0700 [thread overview]
Message-ID: <ZmC0_4ZN---IZEdk@google.com> (raw)
In-Reply-To: <20240122085354.9510-5-binbin.wu@linux.intel.com>
On Mon, Jan 22, 2024, Binbin Wu wrote:
> + if (this_cpu_has(X86_FEATURE_LA57) && read_cr4() & X86_CR4_LA57)
Checking for feature support seems superfluous, e.g. LA57 should never be set if
it's unsupported. Then you can do
lam_mask = is_la57_enabled() ? LAM57_MASK : LAM48_MASK;
> + lam_mask = LAM57_MASK;
> +
> + vaddr = alloc_vpage();
> + install_page(current_page_table(), virt_to_phys(alloc_page()), vaddr);
> + /*
> + * Since the stack memory address in KUT doesn't follow kernel address
> + * space partition rule, reuse the memory address for descriptor and
> + * the target address in the descriptor of invvpid.
> + */
> + operand = (struct invvpid_operand *)vaddr;
Why bother backing the virtual address? MOV needs a valid translation, but
INVVPID does not (ditto for INVLPG and INVPCID, though it might be simpler and
easier to just use the allocated address for those).
> + operand->vpid = 0xffff;
> + operand->gla = (u64)vaddr;
> + operand = (struct invvpid_operand *)set_la_non_canonical((u64)operand,
> + lam_mask);
> + fault = test_for_exception(GP_VECTOR, ds_invvpid, operand);
> + report(!fault, "INVVPID (LAM on): tagged operand");
next prev parent reply other threads:[~2024-06-05 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 8:53 [kvm-unit-tests PATCH v6 0/4] x86: Add test cases for LAM Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 1/4] x86: Allow setting of CR3 LAM bits if LAM supported Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 2/4] x86: Add test case for LAM_SUP Binbin Wu
2024-06-05 18:24 ` Sean Christopherson
2024-06-18 5:48 ` Binbin Wu
2024-06-18 6:37 ` Binbin Wu
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 3/4] x86: Add test cases for LAM_{U48,U57} Binbin Wu
2024-06-05 18:53 ` Sean Christopherson
2024-01-22 8:53 ` [kvm-unit-tests PATCH v6 4/4] x86: Add test case for INVVPID with LAM Binbin Wu
2024-06-05 18:57 ` Sean Christopherson [this message]
2024-06-18 5:55 ` Binbin Wu
2024-06-24 8:20 ` 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=ZmC0_4ZN---IZEdk@google.com \
--to=seanjc@google.com \
--cc=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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.