public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: BrillyWu@viatech.com.cn
Cc: mtosatti@redhat.com, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: Add CPUID support for VIA CPU
Date: Wed, 27 Apr 2011 11:48:26 +0300	[thread overview]
Message-ID: <4DB7D85A.6030600@redhat.com> (raw)
In-Reply-To: <C4F7CD9A92DBFF48AD8779355CD4D7890D8197@exchsg04.s3graphics.com>

On 04/25/2011 08:55 AM, BrillyWu@viatech.com.cn wrote:
> >  On 04/21/2011 01:06 PM, BrillyWu@viatech.com.cn wrote:
> >  >  So,the conclusion is:
> >  >
> >  >  Only VIA C7 CPUs have dependency on EFLAGS[30], but they do
> >  not support VT-X technology, so kvm can not run on it and the issue
> >  about EFLAGS[30] will not occur.
> >  >  VIA Nano CPUs support VT-X technology and can run kvm, but
> >  they have no dependency on EFLAGS[30] (EFLAGS[30] is kept cleared), so
> >  the issue about EFLAGS[30] will not appear, too.
> >  >
> >
> >  Thanks for the clarification.  The patch however does not apply.
> >  Please regenerate it against kvm.git master branch, see
> >  http://www.linux-kvm.org/page/Code.
> >
>
> OK. I have regenerate it as follows. Please check it, thank you!
>

Applied, thanks.

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


  reply	other threads:[~2011-04-27  8:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13  3:26 [PATCH] KVM: Add CPUID support for VIA CPU BrillyWu
2011-04-13  8:59 ` Avi Kivity
2011-04-13 11:05   ` BrillyWu
2011-04-13 11:32     ` Avi Kivity
2011-04-14  3:14       ` BrillyWu
2011-04-14  7:48         ` Avi Kivity
2011-04-14  9:54           ` BrillyWu
2011-04-14 10:07             ` Avi Kivity
2011-04-21 10:06               ` BrillyWu
2011-04-24  7:18                 ` Avi Kivity
2011-04-25  5:55                   ` BrillyWu
2011-04-27  8:48                     ` Avi Kivity [this message]
2011-04-28  1:27                       ` [PATCH] qemu-kvm: " BrillyWu
2011-04-14  3:59       ` [PATCH v2] KVM: " 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=4DB7D85A.6030600@redhat.com \
    --to=avi@redhat.com \
    --cc=BrillyWu@viatech.com.cn \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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