From: "Liu, Jingqi" <jingqi.liu@intel.com>
To: Chao Gao <chao.gao@intel.com>, <kvm@vger.kernel.org>
Cc: Jiaan Lu <jiaan.lu@intel.com>,
Paolo Bonzini <pbonzini@redhat.com>,
"Shuah Khan" <shuah@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
"Borislav Petkov" <bp@suse.de>,
Pawan Gupta <pawan.kumar.gupta@linux.intel.com>,
"Zhang Chen" <chen.zhang@intel.com>,
Daniel Sneddon <daniel.sneddon@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [RFC PATCH v2 10/11] KVM: selftests: Add tests for virtual enumeration/mitigation MSRs
Date: Mon, 22 May 2023 17:39:41 +0800 [thread overview]
Message-ID: <4f548084-3739-b0b0-8a18-1384393fbfe1@intel.com> (raw)
In-Reply-To: <20230414062545.270178-11-chao.gao@intel.com>
On 4/14/2023 2:25 PM, Chao Gao wrote:
> Three virtual MSRs added for guest to report the usage of software
Seems it's better like below.
s/Three virtual MSRs added/Add three virtual MSRs ?
> mitigations. They are enumerated in an architectural way. Try to
> access the three MSRs to ensure the behavior is expected:
> Specifically,
>
> 1. below three cases should cause #GP:
> * access to a non-present MSR
> * write to read-only MSRs
> * toggling reserved bit of a writeable MSR
>
> 2. rdmsr/wrmsr in other cases should succeed
>
> 3. rdmsr should return the value last written
>
> Signed-off-by: Chao Gao <chao.gao@intel.com>
> ---
Thanks,
Jingqi
next prev parent reply other threads:[~2023-05-22 9:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 6:25 [RFC PATCH v2 00/11] Intel IA32_SPEC_CTRL Virtualization Chao Gao
2023-04-14 6:25 ` [RFC PATCH v2 10/11] KVM: selftests: Add tests for virtual enumeration/mitigation MSRs Chao Gao
2023-05-22 9:39 ` Liu, Jingqi [this message]
2023-04-14 6:25 ` [RFC PATCH v2 11/11] KVM: selftests: Add tests for IA32_SPEC_CTRL MSR Chao Gao
2023-04-14 9:51 ` [RFC PATCH v2 00/11] Intel IA32_SPEC_CTRL Virtualization Binbin Wu
2023-04-14 22:10 ` Pawan Gupta
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=4f548084-3739-b0b0-8a18-1384393fbfe1@intel.com \
--to=jingqi.liu@intel.com \
--cc=acme@redhat.com \
--cc=bp@suse.de \
--cc=chao.gao@intel.com \
--cc=chen.zhang@intel.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=jiaan.lu@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=pawan.kumar.gupta@linux.intel.com \
--cc=pbonzini@redhat.com \
--cc=shuah@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