All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: "Xu, Jiajun" <jiajun.xu@intel.com>,
	"'kvm@vger.kernel.org'" <kvm@vger.kernel.org>
Subject: Re: Biweekly KVM Test report, kernel 0c7771... userspace 1223a0...
Date: Mon, 30 Mar 2009 16:55:05 +0300	[thread overview]
Message-ID: <49D0CF39.50009@redhat.com> (raw)
In-Reply-To: <20090330111756.GC26627@amit-x200.pnq.redhat.com>

Amit Shah wrote:
> On (Mon) Mar 30 2009 [10:07:58], Avi Kivity wrote:
>
>   
>>> 1. perfctr wrmsr warning when booting 64bit RHEl5.3
>>> https://sourceforge.net/tracker/?func=detail&aid=2721640&group_id=180599&atid=893831
>>>       
>> This is the architectural performance counting msr which was enabled in  
>> 4f76231 (KVM: x86: Ignore reads to EVNTSEL MSRs).  Amit, can you check  
>> if appropriate cpuid leaf 10 reporting will fix this?
>>     
>
> We already report 0s for the cpuid leaf 10; we need to report 0x3f in
> EBX for leaf 10 to denote events corresponding to the bits aren't
> available.
>
> I checked and it didn't help (we can't rely on guests to abide by cpuid
> flags)
>   

I see this in the code:

>         /*
>          * Check whether the Architectural PerfMon supports
>          * Unhalted Core Cycles Event or not.
>          * NOTE: Corresponding bit = 0 in ebx indicates event present.
>          */
>         cpuid(10, &(eax.full), &ebx, &unused, &unused);
>         if ((eax.split.mask_length < 
> (ARCH_PERFMON_UNHALTED_CORE_CYCLES_INDEX+1)) ||
>             (ebx & ARCH_PERFMON_UNHALTED_CORE_CYCLES_PRESENT))
>                 return 0;
>

So I think it can be done.

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


  reply	other threads:[~2009-03-30 13:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30  2:22 Biweekly KVM Test report, kernel 0c7771... userspace 1223a0 Xu, Jiajun
2009-03-30  7:07 ` Avi Kivity
2009-03-30 11:17   ` Amit Shah
2009-03-30 13:55     ` Avi Kivity [this message]
2009-03-30 14:48       ` Amit Shah
2009-03-30 15:02         ` Avi Kivity
2009-03-31  8:56           ` Amit Shah

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=49D0CF39.50009@redhat.com \
    --to=avi@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=jiajun.xu@intel.com \
    --cc=kvm@vger.kernel.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.