public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sheng Yang <sheng@linux.intel.com>
Cc: kvm@vger.kernel.org, "Hao, Xudong" <xudong.hao@intel.com>
Subject: Re: KVM Test report, kernel e6a9246... qemu 94f964d...
Date: Tue, 07 Sep 2010 16:23:29 +0300	[thread overview]
Message-ID: <4C863CD1.7020501@redhat.com> (raw)
In-Reply-To: <4C8630A2.9040706@redhat.com>

  On 09/07/2010 03:31 PM, Avi Kivity wrote:
>  On 09/07/2010 03:04 PM, Avi Kivity wrote:
>>  On 09/07/2010 02:27 PM, Avi Kivity wrote:
>>>  On 09/07/2010 11:54 AM, Sheng Yang wrote:
>>>>
>>>> BTW: the bad commit is: c94c3ba901f87115cf574044e7faabfb1d0251fb 
>>>> "KVM: Don't
>>>> save/restore MSR_IA32_PERF_STATUS", but I haven't figured out the 
>>>> reason yet.
>>>
>>> Confirmed.  Strange!
>>>
>>
>> It's incredibly slow.  Did we disable the cpu cache somehow?  Maybe 
>> through the page tables?
>>
>
> PAT = 0.
>

Patch posted - qemu didn't reset PAT correctly, but this worked before 
c94c3ba90 since setting MSR_IA32_PERF_STATUS failed (and qemu didn't 
check the error code).

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


  reply	other threads:[~2010-09-07 13:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  3:05 KVM Test report, kernel e6a9246... qemu 94f964d Hao, Xudong
2010-09-06  6:55 ` Avi Kivity
2010-09-06  6:59   ` Hao, Xudong
2010-09-06  8:04     ` Avi Kivity
2010-09-06  8:08       ` Hao, Xudong
2010-09-06  8:56         ` Avi Kivity
2010-09-07  0:51           ` Hao, Xudong
2010-09-07  7:22           ` Hao, Xudong
2010-09-07  8:15             ` Avi Kivity
2010-09-07  8:54               ` Sheng Yang
2010-09-07 11:27                 ` Avi Kivity
2010-09-07 12:04                   ` Avi Kivity
2010-09-07 12:31                     ` Avi Kivity
2010-09-07 13:23                       ` Avi Kivity [this message]
2010-09-08  0:35                         ` Sheng Yang

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=4C863CD1.7020501@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=sheng@linux.intel.com \
    --cc=xudong.hao@intel.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