From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] Remove MSR_P6_{EVNTSEL0,PERFCTR0} from printk warning list.
Date: Thu, 01 Jul 2010 16:41:14 +0200 [thread overview]
Message-ID: <4C2CA90A.6070201@redhat.com> (raw)
In-Reply-To: <4C2CA84A.4090506@redhat.com>
On 07/01/10 16:38, Avi Kivity wrote:
> On 06/30/2010 05:27 PM, Jes.Sorensen@redhat.com wrote:
>> From: Jes Sorensen<Jes.Sorensen@redhat.com>
>>
>> MSR_P6_EVNTSEL0 and MSR_P6_PERFCTR0 are used to probe for the P6 PMU
>> for older family 6 CPUs, which is also the default in QEMU. Ie. per
>> default we get the noise of these warnings in dmesg, confusing users
>> for no reason.
>
> For the reason, see the comment above. The guest may be trying to do
> something with the counters and expect them to work. Without the
> warning we'd have no idea we are knowningly misemulating something.
Saw it, which is why I only suggest we remove EVNTSEL0 and PERFCTR0 but
not the others. If the guest is expecting normal operation it is likely
to use more than just the first.
People are reporting these triggering in dmesg for both Linux and
Windows guests btw.
We could put them so the two in question only trigger with a debug flag
or something like that?
Cheers,
Jes
next prev parent reply other threads:[~2010-07-01 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 14:27 [PATCH] Remove MSR_P6_{EVNTSEL0,PERFCTR0} from printk warning list Jes.Sorensen
2010-07-01 14:38 ` Avi Kivity
2010-07-01 14:41 ` Jes Sorensen [this message]
2010-07-01 14:44 ` Avi Kivity
2010-07-01 14:47 ` Jes Sorensen
2010-07-01 15:02 ` Avi Kivity
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=4C2CA90A.6070201@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=avi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox