kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Liu, Jinsong" <jinsong.liu@intel.com>
Cc: "mtosatti@redhat.com" <mtosatti@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] X86: expose latest Intel cpu new features to guest
Date: Mon, 28 Nov 2011 11:25:32 +0200	[thread overview]
Message-ID: <4ED3538C.7000609@redhat.com> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E28707E5BD8@shsmsx502.ccr.corp.intel.com>

On 11/28/2011 07:10 AM, Liu, Jinsong wrote:
> From 8bb5d052825149c211afa92458912bc49a50ee2f Mon Sep 17 00:00:00 2001
> From: Liu, Jinsong <jinsong.liu@intel.com>
> Date: Mon, 28 Nov 2011 03:55:19 -0800
> Subject: [PATCH] X86: expose latest Intel cpu new features to guest
>
> Intel latest cpu add 6 new features, refer http://software.intel.com/file/36945
> The new feature cpuid listed as below:
> 1. FMA		CPUID.EAX=01H:ECX.FMA[bit 12]
> 2. MOVBE	CPUID.EAX=01H:ECX.MOVBE[bit 22]
> 3. BMI1		CPUID.EAX=07H,ECX=0H:EBX.BMI1[bit 3]
> 4. AVX2		CPUID.EAX=07H,ECX=0H:EBX.AVX2[bit 5]
> 5. BMI2		CPUID.EAX=07H,ECX=0H:EBX.BMI2[bit 8]
> 6. LZCNT	CPUID.EAX=80000001H:ECX.LZCNT[bit 5]
>
> This patch expose these features to guest.
> Among them, FMA/MOVBE/LZCNT has already been defined, MOVBE/LZCNT has already been exposed.
> This patch defines BMI1/AVX2/BMI2, and exposes FMA/BMI1/AVX2/BMI2 to guest.
>
>

Thanks, applied.

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


      reply	other threads:[~2011-11-28  9:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-28  5:10 [PATCH] X86: expose latest Intel cpu new features to guest Liu, Jinsong
2011-11-28  9:25 ` Avi Kivity [this message]

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=4ED3538C.7000609@redhat.com \
    --to=avi@redhat.com \
    --cc=jinsong.liu@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).