public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, zamsden@redhat.com
Subject: Re: [PATCH v3 5/8] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID
Date: Tue, 11 May 2010 11:29:08 +0300	[thread overview]
Message-ID: <4BE91554.2030503@redhat.com> (raw)
In-Reply-To: <1273094839-18655-6-git-send-email-glommer@redhat.com>

On 05/06/2010 12:27 AM, Glauber Costa wrote:
> Right now, we were using individual KVM_CAP entities to communicate
> userspace about which cpuids we support. This is suboptimal, since it
> generates a delay between the feature arriving in the host, and
> being available at the guest.
>
> A much better mechanism is to list para features in KVM_GET_SUPPORTED_CPUID.
> This makes userspace automatically aware of what we provide. And if we
> ever add a new cpuid bit in the future, we have to do that again,
> which create some complexity and delay in feature adoption.
>
>
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -1971,6 +1971,23 @@ static void do_cpuid_ent(struct kvm_cpuid_entry2 *entry, u32 function,
>   		}
>   		break;
>   	}
> +	case KVM_CPUID_SIGNATURE: {
> +		char signature[12] = "KVMKVMKVM\0\0";
> +		u32 *sigptr = (u32 *)signature;
> +		entry->eax = 1;
>    

Don't understand where the value for eax comes from.  qemu-kvm-x86.c has 0.

> @@ -2017,6 +2034,19 @@ static int kvm_dev_ioctl_get_supported_cpuid(struct kvm_cpuid2 *cpuid,
>   	for (func = 0x80000001; func<= limit&&  nent<  cpuid->nent; ++func)
>   		do_cpuid_ent(&cpuid_entries[nent], func, 0,
>   			&nent, cpuid->nent);
> +
> +	
> +
> +	r = -E2BIG;
> +	if (nent>= cpuid->nent)
> +		goto out_free;
> +
> +	do_cpuid_ent(&cpuid_entries[nent], KVM_CPUID_SIGNATURE, 0,&nent,
> +		     cpuid->nent);
>    

Need a check here too, or the next call can overflow.  Would have been 
better to make do_cpuid_ent() check and return an error.

> +
> +	do_cpuid_ent(&cpuid_entries[nent], KVM_CPUID_FEATURES, 0,&nent,
> +		     cpuid->nent);
> +
>   	r = -E2BIG;
>   	if (nent>= cpuid->nent)
>   		goto out_free;
>    


-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2010-05-11  8:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 21:27 [PATCH v3 0/8] pvclock fixes - v3 Glauber Costa
2010-05-05 21:27 ` [PATCH v3 1/8] Enable pvclock flags in vcpu_time_info structure Glauber Costa
2010-05-05 21:27   ` [PATCH v3 2/8] Add a global synchronization point for pvclock Glauber Costa
2010-05-05 21:27     ` [PATCH v3 3/8] change msr numbers for kvmclock Glauber Costa
2010-05-05 21:27       ` [PATCH v3 4/8] add new KVMCLOCK cpuid feature Glauber Costa
2010-05-05 21:27         ` [PATCH v3 5/8] export paravirtual cpuid flags in KVM_GET_SUPPORTED_CPUID Glauber Costa
2010-05-05 21:27           ` [PATCH v3 6/8] Try using new kvm clock msrs Glauber Costa
2010-05-05 21:27             ` [PATCH v3 7/8] don't compute pvclock adjustments if we trust the tsc Glauber Costa
2010-05-05 21:27               ` [PATCH v3 8/8] Tell the guest we'll warn it about tsc stability Glauber Costa
2010-05-11  8:29           ` Avi Kivity [this message]
2010-05-11  8:35 ` [PATCH v3 0/8] pvclock fixes - v3 Avi Kivity

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=4BE91554.2030503@redhat.com \
    --to=avi@redhat.com \
    --cc=glommer@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zamsden@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