All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Shah <amit.shah@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, aliguori@us.ibm.com
Subject: Re: v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd
Date: Thu, 15 Jan 2009 15:58:57 +0530	[thread overview]
Message-ID: <20090115102857.GA25534@amit-x200.pnq.redhat.com> (raw)
In-Reply-To: <496F07C1.6050605@redhat.com>

On Thu, Jan 15, 2009 at 11:54:09AM +0200, Avi Kivity wrote:
> Amit Shah wrote:
>> These patches add support for cpuid functions that take a 'count' parameter
>> in addition to the function number. With these patches, KVM can run a VM
>> started with a newer CPU type (coreduo, core2duo). These patches also pave
>> way for a "host" CPU type, where we could pass the CPU type of the current
>> host to the VM.
>>
>> v3 uses the as-yet unused KVM_SET_CPUID2 interface, which was written to
>> support this functionality. Since we rely on kernel versions 2.6.25 at a
>> minimum for KVM and the SET_CPUID2 interface was introduced in 2.6.25, we're
>> safe with this.
>
> Looks good.  Note that function 2 also needs special treatment.

Yes; I'll add that support as well.

Thanks,
Amit

WARNING: multiple messages have this Message-ID (diff)
From: Amit Shah <amit.shah@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] Re: v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd
Date: Thu, 15 Jan 2009 15:58:57 +0530	[thread overview]
Message-ID: <20090115102857.GA25534@amit-x200.pnq.redhat.com> (raw)
In-Reply-To: <496F07C1.6050605@redhat.com>

On Thu, Jan 15, 2009 at 11:54:09AM +0200, Avi Kivity wrote:
> Amit Shah wrote:
>> These patches add support for cpuid functions that take a 'count' parameter
>> in addition to the function number. With these patches, KVM can run a VM
>> started with a newer CPU type (coreduo, core2duo). These patches also pave
>> way for a "host" CPU type, where we could pass the CPU type of the current
>> host to the VM.
>>
>> v3 uses the as-yet unused KVM_SET_CPUID2 interface, which was written to
>> support this functionality. Since we rely on kernel versions 2.6.25 at a
>> minimum for KVM and the SET_CPUID2 interface was introduced in 2.6.25, we're
>> safe with this.
>
> Looks good.  Note that function 2 also needs special treatment.

Yes; I'll add that support as well.

Thanks,
Amit

  reply	other threads:[~2009-01-15 10:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 16:41 v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd Amit Shah
2009-01-14 16:41 ` [Qemu-devel] " Amit Shah
2009-01-14 16:41 ` [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Amit Shah
2009-01-14 16:41   ` [Qemu-devel] " Amit Shah
2009-01-14 16:41   ` [PATCH 2/2] KVM: Fetch sub-leaf cpuid values for functions 4, 0xb, 0xd Amit Shah
2009-01-14 16:41     ` [Qemu-devel] " Amit Shah
2009-01-15 21:54   ` [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Anthony Liguori
2009-01-15 21:54     ` [Qemu-devel] " Anthony Liguori
2009-01-16 11:17     ` KVM: support for 'count' in CPUID functions 4, 0xb and 0xd Amit Shah
2009-01-16 11:17       ` [Qemu-devel] " Amit Shah
2009-01-16 11:17       ` [PATCH 1/2] KVM: CPUID takes ecx as input value for some functions Amit Shah
2009-01-16 11:17         ` [Qemu-devel] " Amit Shah
2009-01-16 11:17         ` [PATCH 2/2] KVM: Fetch sub-leaf cpuid values for functions 4, 0xb, 0xd Amit Shah
2009-01-16 11:17           ` [Qemu-devel] " Amit Shah
2009-01-15  9:54 ` v3: KVM: support for 'count' in CPUID functions 4, 0xb and 0xd Avi Kivity
2009-01-15  9:54   ` [Qemu-devel] " Avi Kivity
2009-01-15 10:28   ` Amit Shah [this message]
2009-01-15 10:28     ` Amit Shah

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=20090115102857.GA25534@amit-x200.pnq.redhat.com \
    --to=amit.shah@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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 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.