qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: BrillyWu <brillywu@gmail.com>, Blue Swirl <blauwirbel@gmail.com>
Cc: kvm@vger.kernel.org, KaryJin@viatech.com.cn, mst@redhat.com,
	mtosatti@redhat.com, BrillyWu@viatech.com.cn,
	qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU
Date: Tue, 31 May 2011 08:11:21 +0200	[thread overview]
Message-ID: <4DE48689.7070606@web.de> (raw)
In-Reply-To: <BANLkTikq3-aSKTSGY4EdtCyF8QgHyobQsw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]

On 2011-05-31 03:25, BrillyWu wrote:
> Hi, Jan
> 
>> patch which has
>>> been checked. It can be compiled without any error and work
>> normally.
>>>         The patch v3 is here now.
>>
>> The above text can't be used as a commit log, so this needs to be
>> fixed.
>> Moreover, your patch still contains at least on style issues
>> scripts/checkpatch.pl should have caught. Are you sure you ran it?
>>
> 
> I am sure I have checked it with the scripts/checkpatch.pl, and it
> shows no error or warning. Maybe I should check whether my windows
> editor and  mail client can work well before sending it to you. I 'm
> sorry.

Sorry, you are right. Your patch revealed a bug in the checkpatch script.

Blue, this does not trigger the missing braces warning:

@@ -1035,8 +1052,17 @@ void cpu_x86_cpuid(CPUX86State *env, uin
 {
     /* test if maximum index reached */
     if (index & 0x80000000) {
-        if (index > env->cpuid_xlevel)
-            index = env->cpuid_level;
+        if (index > env->cpuid_xlevel) {
+            if (env->cpuid_xlevel2 > 0) {
+                /* Handle the Centaur's CPUID instruction. */
+                if (index > env->cpuid_xlevel2) {
+                    index = env->cpuid_xlevel2;
+                } else if (index < 0xC0000000) {
+                    index = env->cpuid_xlevel;
+                }
+            } else
+                index =  env->cpuid_xlevel;
+        }
     } else {
         if (index > env->cpuid_level)
             index = env->cpuid_level;


> OK, I will use the previous commit log, and send it to you in the new thread.

Thanks. I think it would be fair to fix up the braces on commit now.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 259 bytes --]

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

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10  8:02 [Qemu-devel] [PATCH uq/master V2] kvm: Add CPUID support for VIA CPU BrillyWu
2011-05-11 11:50 ` Avi Kivity
2011-05-28 10:28 ` Jan Kiszka
2011-05-28 16:20 ` Jan Kiszka
2011-05-30  4:02   ` BrillyWu
2011-05-30  7:40     ` BrillyWu
2011-05-30  7:47       ` Jan Kiszka
2011-05-30  8:59       ` BrillyWu
2011-05-30 10:45         ` Jan Kiszka
2011-05-31  1:25           ` BrillyWu
2011-05-31  6:11             ` Jan Kiszka [this message]
2011-05-31  7:39               ` BrillyWu
2011-05-31  7:50                 ` Jan Kiszka
2011-05-31  8:22                   ` 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=4DE48689.7070606@web.de \
    --to=jan.kiszka@web.de \
    --cc=BrillyWu@viatech.com.cn \
    --cc=KaryJin@viatech.com.cn \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=brillywu@gmail.com \
    --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 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).