mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jing Liu <jing2.liu@linux.intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH 5/5] KVM: cpuid: remove has_leaf_count from struct kvm_cpuid_param
Date: Mon, 8 Jul 2019 15:09:01 +0800	[thread overview]
Message-ID: <bb5e81f4-bb34-2841-0fa1-63876b97e54c@linux.intel.com> (raw)
In-Reply-To: <20190704140715.31181-6-pbonzini@redhat.com>

Hi Paolo,

On 7/4/2019 10:07 PM, Paolo Bonzini wrote:
> The has_leaf_count member was originally added for KVM's paravirtualization
> CPUID leaves.  However, since then the leaf count _has_ been added to those
> leaves as well, so we can drop that special case.
> 
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
[...]
> @@ -835,11 +834,10 @@ int kvm_dev_ioctl_get_cpuid(struct kvm_cpuid2 *cpuid,
>   	int limit, nent = 0, r = -E2BIG, i;
>   	u32 func;
>   	static const struct kvm_cpuid_param param[] = {
> -		{ .func = 0, .has_leaf_count = true },
> -		{ .func = 0x80000000, .has_leaf_count = true },
> -		{ .func = 0xC0000000, .qualifier = is_centaur_cpu, .has_leaf_count = true },
> +		{ .func = 0 },
> +		{ .func = 0x80000000 },
> +		{ .func = 0xC0000000, .qualifier = is_centaur_cpu },

>   		{ .func = KVM_CPUID_SIGNATURE },
> -		{ .func = KVM_CPUID_FEATURES },

It seems the two func are introduced by 2b5e97e, as paravirtual cpuid.
But when searching KVM_CPUID_SIGNATURE, there seems no caller requesting
this cpuid. Meanwhile, I felt curious if KVM_CPUID_FEATURES is still in 
use but it seems kvm_update_cpuid() uses that. Not sure which spec 
introduces the latest pv cpuid.

Thanks,
Jing

[...]

  reply	other threads:[~2019-07-08  7:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-04 14:07 [PATCH 0/5] KVM: cpuid: cleanups, simplify multi-index CPUID leaves Paolo Bonzini
2019-07-04 14:07 ` [PATCH 1/5] KVM: cpuid: do_cpuid_ent works on a whole CPUID function Paolo Bonzini
2019-07-08  7:05   ` Jing Liu
2019-07-04 14:07 ` [PATCH 2/5] KVM: cpuid: extract do_cpuid_7_mask and support multiple subleafs Paolo Bonzini
2019-07-08  7:07   ` Jing Liu
2019-07-10  6:30     ` Paolo Bonzini
2019-07-10  7:32       ` Jing Liu
2019-07-10  7:48         ` Paolo Bonzini
2019-07-04 14:07 ` [PATCH 3/5] KVM: cpuid: set struct kvm_cpuid_entry2 flags in do_cpuid_1_ent Paolo Bonzini
2019-07-04 14:07 ` [PATCH 4/5] KVM: cpuid: rename do_cpuid_1_ent Paolo Bonzini
2019-07-04 14:07 ` [PATCH 5/5] KVM: cpuid: remove has_leaf_count from struct kvm_cpuid_param Paolo Bonzini
2019-07-08  7:09   ` Jing Liu [this message]
2019-07-10  6:34     ` Paolo Bonzini

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=bb5e81f4-bb34-2841-0fa1-63876b97e54c@linux.intel.com \
    --to=jing2.liu@linux.intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome