From: Xiao Guangrong <guangrong.xiao@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Huaitong Han <huaitong.han@intel.com>,
gleb@kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH V4 1/7] KVM, pkeys: expose CPUID/CR4 to guest
Date: Tue, 8 Mar 2016 15:39:55 +0800 [thread overview]
Message-ID: <56DE81CB.3040505@linux.intel.com> (raw)
In-Reply-To: <56DCBB30.7010107@redhat.com>
On 03/07/2016 07:20 AM, Paolo Bonzini wrote:
>
>
> On 06/03/2016 08:15, Xiao Guangrong wrote:
>>> + /* cpuid 7.0.ecx*/
>>> + const u32 kvm_supported_word11_x86_features = F(PKU) | 0 /*OSPKE*/;
>>> +
>>>
>>> cpuid_mask(&entry->ebx, 9);
>>> // TSC_ADJUST is emulated
>>> entry->ebx |= F(TSC_ADJUST);
>>> - } else
>>> + entry->ecx &= kvm_supported_word11_x86_features;
>>> + cpuid_mask(&entry->ecx, 13);
>>
>> Can we use a meaningful name defined by cpuid_leafs instead of the raw
>> number?
>
> This is not a cpuid leaf number, it's the Linux feature word number. In
> other words, the "11" in kvm_supported_word11_x86_features should have
> matched the "13" in cpuid_mask(&entry->ecx, 13).
But i noticed kernel uses the more meaningful name to update
boot_cpu_data.x86_capability[]:
$ git grep x86_capability arch/x86/
......
arch/x86/kernel/cpu/centaur.c: c->x86_capability[CPUID_C000_0001_EDX] = cpuid_edx(0xC0000001);
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_1_ECX] = ecx;
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_1_EDX] = edx;
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_7_0_EBX] = ebx;
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_6_EAX] = cpuid_eax(0x00000006);
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_D_1_EAX] = eax;
arch/x86/kernel/cpu/common.c: c->x86_capability[CPUID_F_0_EDX] = edx;
.....
Why not follow it in KVM?
next prev parent reply other threads:[~2016-03-08 7:40 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 11:27 [PATCH V4 0/7] KVM, pkeys: add memory protection-key support Huaitong Han
2016-03-05 11:27 ` [PATCH V4 1/7] KVM, pkeys: expose CPUID/CR4 to guest Huaitong Han
2016-03-06 7:15 ` Xiao Guangrong
2016-03-06 23:20 ` Paolo Bonzini
2016-03-08 7:39 ` Xiao Guangrong [this message]
2016-03-08 7:58 ` Paolo Bonzini
2016-03-05 11:27 ` [PATCH V4 2/7] KVM, pkeys: disable pkeys for guests in non-paging mode Huaitong Han
2016-03-06 7:19 ` Xiao Guangrong
2016-03-08 12:09 ` Yang Zhang
2016-03-08 12:11 ` Paolo Bonzini
2016-03-08 13:02 ` Yang Zhang
2016-03-05 11:27 ` [PATCH V4 3/7] KVM, pkeys: update memeory permission bitmask for pkeys Huaitong Han
2016-03-06 7:42 ` Xiao Guangrong
2016-03-06 23:14 ` Paolo Bonzini
2016-03-08 7:35 ` Xiao Guangrong
2016-03-08 8:29 ` Paolo Bonzini
2016-03-08 9:19 ` Xiao Guangrong
2016-03-08 10:01 ` Paolo Bonzini
2016-03-09 5:03 ` Xiao Guangrong
2016-03-09 8:10 ` Paolo Bonzini
2016-03-05 11:27 ` [PATCH V4 4/7] KVM, pkeys: add pkeys support for permission_fault logic Huaitong Han
2016-03-06 8:00 ` Xiao Guangrong
2016-03-06 20:36 ` Paolo Bonzini
2016-03-06 23:29 ` Paolo Bonzini
2016-03-08 5:57 ` Xiao Guangrong
2016-03-05 11:27 ` [PATCH V4 5/7] KVM, pkeys: Add pkeys support for gva_to_gpa funcions Huaitong Han
2016-03-06 8:01 ` Xiao Guangrong
2016-03-06 21:33 ` Paolo Bonzini
2016-03-05 11:27 ` [PATCH V4 6/7] KVM, pkeys: add pkeys support for xsave state Huaitong Han
2016-03-06 8:27 ` Xiao Guangrong
2016-03-05 11:27 ` [PATCH V4 7/7] KVM, pkeys: disable PKU feature without ept Huaitong Han
2016-03-06 9:28 ` Xiao Guangrong
2016-03-06 20:32 ` Paolo Bonzini
2016-03-08 5:54 ` Xiao Guangrong
2016-03-08 8:47 ` Paolo Bonzini
2016-03-08 9:32 ` Xiao Guangrong
2016-03-08 10:02 ` Paolo Bonzini
2016-03-09 5:51 ` Xiao Guangrong
2016-03-09 6:37 ` Yang Zhang
2016-03-09 7:21 ` Xiao Guangrong
2016-03-09 7:41 ` Yang Zhang
2016-03-09 7:50 ` Xiao Guangrong
2016-03-09 8:00 ` Yang Zhang
2016-03-09 8:05 ` Xiao Guangrong
2016-03-09 8:18 ` Paolo Bonzini
2016-03-09 8:13 ` Paolo Bonzini
2016-03-09 6:24 ` Yang 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=56DE81CB.3040505@linux.intel.com \
--to=guangrong.xiao@linux.intel.com \
--cc=gleb@kernel.org \
--cc=huaitong.han@intel.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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.