From: Avi Kivity <avi@redhat.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Pekka Enberg <penberg@kernel.org>,
"Yan, Zheng" <zheng.z.yan@linux.intel.com>,
Sasha Levin <levinsasha928@gmail.com>,
Asias He <asias.hejun@gmail.com>,
Cyrill Gorcunov <gorcunov@gmail.com>, Ingo Molnar <mingo@elte.hu>,
KVM General <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: Re: perf uncore & lkvm woes
Date: Thu, 16 Aug 2012 14:25:05 +0300 [thread overview]
Message-ID: <502CD891.5030102@redhat.com> (raw)
In-Reply-To: <1345115846.29668.16.camel@twins>
On 08/16/2012 02:17 PM, Peter Zijlstra wrote:
> On Thu, 2012-08-16 at 14:06 +0300, Avi Kivity wrote:
>
>> Another option is to deal with them on the host side. That has the
>> benefit of working with non-Linux guests too.
>
> Right, its an insane amount of MSRs though, but it could be done if
> someone takes the time to enumerate them all.
It's tedious but that's life.
>
> If KVM then simply ignores all writes and returns all 0 on read we can
> do the same we do for the regular PMU in check_hw_exists().
>
>> We can just ignore the MSR and print some warning.
>
> If you don't mind printing a warning every time a Linux guest boots ;-)
We can printk_once() it, or only under debug, now that we have dynamic
debug. We also need to print the warning only if the counter is
enabled. Will Linux configure uncore counters by default (why and which?)
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-08-16 11:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 7:01 perf uncore & lkvm woes Pekka Enberg
2012-08-16 7:07 ` Cyrill Gorcunov
2012-08-16 7:16 ` Cyrill Gorcunov
2012-08-16 7:16 ` Pekka Enberg
2012-08-16 7:19 ` Peter Zijlstra
2012-08-16 7:38 ` Yan, Zheng
2012-08-16 7:41 ` Pekka Enberg
2012-08-16 7:46 ` Cyrill Gorcunov
2012-08-16 8:45 ` Avi Kivity
2012-08-16 9:06 ` Cyrill Gorcunov
2012-08-16 9:23 ` Pekka Enberg
2012-08-16 8:40 ` Avi Kivity
2012-08-16 11:06 ` Avi Kivity
2012-08-16 11:17 ` Peter Zijlstra
2012-08-16 11:25 ` Avi Kivity [this message]
2012-08-17 1:40 ` Yan, Zheng
2012-08-17 6:56 ` Peter Zijlstra
2012-08-19 9:55 ` Avi Kivity
2012-08-20 4:15 ` Yan, Zheng
2012-08-20 8:49 ` Avi Kivity
2012-08-21 1:11 ` Yan, Zheng
2012-08-21 8:32 ` Avi Kivity
2012-08-21 9:07 ` Yan, Zheng
2012-08-20 5:30 ` Yan, Zheng
2012-08-20 8:48 ` Avi Kivity
2012-08-21 7:11 ` Peter Zijlstra
2012-08-21 8:34 ` Avi Kivity
2012-08-21 10:35 ` Peter Zijlstra
2012-08-22 8:53 ` Avi Kivity
2012-08-16 14:28 ` David Ahern
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=502CD891.5030102@redhat.com \
--to=avi@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=asias.hejun@gmail.com \
--cc=gleb@redhat.com \
--cc=gorcunov@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=mingo@elte.hu \
--cc=penberg@kernel.org \
--cc=zheng.z.yan@linux.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 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.