All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: BrillyWu <brillywu@gmail.com>
Cc: kvm@vger.kernel.org, karyjin@viatech.com.cn, mst@redhat.com,
	mtosatti@redhat.com,
	"BrillyWu@viatech.com.cn" <brillywu@viatech.com.cn>,
	qemu-devel@nongnu.org, jan.kiszka@web.de
Subject: Re: [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU
Date: Wed, 11 May 2011 14:50:14 +0300	[thread overview]
Message-ID: <4DCA77F6.1070209@redhat.com> (raw)
In-Reply-To: <BANLkTimzTSU7A-b9yc9H35b1szfL4z7H-A@mail.gmail.com>

On 05/10/2011 11:02 AM, BrillyWu wrote:
> From: BrillyWu<brillywu@viatech.com.cn>
>
> When KVM is running on VIA CPU with host cpu's model, the
> feautures of VIA CPU will be passed into kvm guest by calling
> the CPUID instruction for Centaur.
>

Applied, thanks.

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

WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@redhat.com>
To: BrillyWu <brillywu@gmail.com>
Cc: kvm@vger.kernel.org, karyjin@viatech.com.cn, mst@redhat.com,
	mtosatti@redhat.com,
	"BrillyWu@viatech.com.cn" <brillywu@viatech.com.cn>,
	qemu-devel@nongnu.org, jan.kiszka@web.de
Subject: Re: [Qemu-devel] [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU
Date: Wed, 11 May 2011 14:50:14 +0300	[thread overview]
Message-ID: <4DCA77F6.1070209@redhat.com> (raw)
In-Reply-To: <BANLkTimzTSU7A-b9yc9H35b1szfL4z7H-A@mail.gmail.com>

On 05/10/2011 11:02 AM, BrillyWu wrote:
> From: BrillyWu<brillywu@viatech.com.cn>
>
> When KVM is running on VIA CPU with host cpu's model, the
> feautures of VIA CPU will be passed into kvm guest by calling
> the CPUID instruction for Centaur.
>

Applied, thanks.

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

  reply	other threads:[~2011-05-11 11:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  8:02 [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU BrillyWu
2011-05-10  8:02 ` [Qemu-devel] " BrillyWu
2011-05-11 11:50 ` Avi Kivity [this message]
2011-05-11 11:50   ` Avi Kivity
2011-05-28 10:28 ` Jan Kiszka
2011-05-28 10:28   ` [Qemu-devel] " Jan Kiszka
2011-05-28 16:20 ` Jan Kiszka
2011-05-28 16:20   ` [Qemu-devel] " Jan Kiszka
2011-05-30  4:02   ` BrillyWu
2011-05-30  4:02     ` [Qemu-devel] " BrillyWu
2011-05-30  7:40     ` BrillyWu
2011-05-30  7:40       ` [Qemu-devel] " BrillyWu
2011-05-30  7:47       ` Jan Kiszka
2011-05-30  7:47         ` [Qemu-devel] " Jan Kiszka
2011-05-30  8:59       ` BrillyWu
2011-05-30  8:59         ` [Qemu-devel] " BrillyWu
2011-05-30 10:45         ` Jan Kiszka
2011-05-30 10:45           ` [Qemu-devel] " Jan Kiszka
2011-05-31  1:25           ` BrillyWu
2011-05-31  1:25             ` [Qemu-devel] " BrillyWu
2011-05-31  6:11             ` Jan Kiszka
2011-05-31  6:11               ` [Qemu-devel] " Jan Kiszka
2011-05-31  7:39               ` BrillyWu
2011-05-31  7:39                 ` [Qemu-devel] " BrillyWu
2011-05-31  7:50                 ` Jan Kiszka
2011-05-31  7:50                   ` [Qemu-devel] " Jan Kiszka
2011-05-31  8:22                   ` BrillyWu
2011-05-31  8:22                     ` [Qemu-devel] " BrillyWu

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=4DCA77F6.1070209@redhat.com \
    --to=avi@redhat.com \
    --cc=brillywu@gmail.com \
    --cc=brillywu@viatech.com.cn \
    --cc=jan.kiszka@web.de \
    --cc=karyjin@viatech.com.cn \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --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 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.