From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Dan Kenigsberg <danken-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [RFC] Expose host cpuid to guest
Date: Wed, 21 Nov 2007 17:11:33 +0200 [thread overview]
Message-ID: <47444AA5.7040807@qumranet.com> (raw)
In-Reply-To: <20071121144128.GA26036-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
Dan Kenigsberg wrote:
> On Wed, Nov 21, 2007 at 01:52:15PM +0200, Avi Kivity wrote:
>
>> Dan Kenigsberg wrote:
>>
>>> These patches expose host CPU features (that are known to work under
>>> KVM) to guests. It makes a couple of benchmarks run faster, and
>>> generally gives kvm's user better info on its host.
>>>
>>> The kernel-space patch adds KVM_GET_SUPPORTED_CPUID ioctl to obtain the
>>> table of cpuid functions supported by the host. The user-space patch
>>> allows fine-tuning this table from the command-line.
>>>
>>> I had to define struct kvm_cpuid2, KVM_SET_CPUID2 etc., because cpuid
>>> functions are a little more complex than just function-value pairs.
>>> commit e9775d0a16097cfb71779cb2fb985fb3e5040dc8
>>> Author: Dan Kenigsberg <danken-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
>>> Date: Sun Nov 18 13:55:26 2007 +0200
>>>
>>> Support -cpu host option. Negotiate cpuid table with userspace.
>>>
>
> I believe the attached two patches apply all your comments.
>
>
Applied kernel patch. Will wait with userspace until next qemu merge
(which is pending qemu-cvs regressions).
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-11-21 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 11:06 [RFC] Expose host cpuid to guest Dan Kenigsberg
[not found] ` <20071121110631.GA14292-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-21 11:21 ` Amit Shah
2007-11-21 11:52 ` Avi Kivity
[not found] ` <47441BEF.4070207-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-21 14:41 ` Dan Kenigsberg
[not found] ` <20071121144128.GA26036-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-21 15:11 ` Avi Kivity [this message]
2007-11-21 23:42 ` Mike Lampard
[not found] ` <200711221012.05384.mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>
2007-11-22 13:01 ` Dan Kenigsberg
[not found] ` <20071122130118.GA14295-iWbx9bcAnq+Hk9JtIoIkgNBPR1lH4CV8@public.gmane.org>
2007-11-22 13:20 ` Mike Lampard
[not found] ` <200711222350.14746.mike-/+b+wjvSUqIxsqv6Oivclw@public.gmane.org>
2007-11-22 13:36 ` Dan Kenigsberg
2007-11-22 13:30 ` Avi Kivity
[not found] ` <47458458.3030104-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-22 13:50 ` Mike Lampard
2007-12-25 15:56 ` [RFC] Expose host cpuid to guest: userspace patch Dan Kenigsberg
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=47444AA5.7040807@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=danken-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.