From: Avi Kivity <avi@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Support for cpuid functions with subleaves
Date: Thu, 15 Jan 2009 11:39:10 +0200 [thread overview]
Message-ID: <496F043E.6000707@redhat.com> (raw)
In-Reply-To: <1231951906-28145-1-git-send-email-amit.shah@redhat.com>
Amit Shah wrote:
> Hello,
>
> v3 of the patch uses the KVM_SET_CPUID2 interface to not cause any userspace
> and kernel incompatibilities.
>
> With these patches applied, I can run a VM with a newer CPU type (core2duo).
>
> Fixes bug #2413430
>
> Please apply
>
Applied both, thanks.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-01-15 9:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-14 16:51 Support for cpuid functions with subleaves Amit Shah
2009-01-14 16:51 ` [PATCH] kvm: libkvm: Add a wrapper for an ioctl for the KVM_SET_CPUID2 interface Amit Shah
2009-01-14 16:51 ` [PATCH] kvm: userspace: Fetch sub-leaf cpuid values for functions 4, 0xb, 0xd Amit Shah
2009-01-15 9:39 ` Avi Kivity [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-13 10:47 Support for cpuid functions with subleaves 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=496F043E.6000707@redhat.com \
--to=avi@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kvm@vger.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