From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Pekka Enberg <penberg@kernel.org>
Cc: 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>,
"Yan, Zheng" <zheng.z.yan@linux.intel.com>
Subject: Re: perf uncore & lkvm woes
Date: Thu, 16 Aug 2012 09:19:45 +0200 [thread overview]
Message-ID: <1345101585.31459.112.camel@twins> (raw)
In-Reply-To: <CAOJsxLHg2idOMTcy_GsSwm8RBt9o1LFMA7KUSCh=Zs=RnvUQXA@mail.gmail.com>
On Thu, 2012-08-16 at 10:01 +0300, Pekka Enberg wrote:
> Has anyone seen this? It's kvmtool/next with 3.6.0-rc1. Looks like we
> are doing uncore_init() on virtualized CPU which breaks boot.
I think you're the first.. I don't normally use kvm if I can at all
avoid it.
But I think its a 'simple' matter of kvm not emulating the entire
hardware. Afaik the uncore isn't enumerated and we simply assume MSR
presence based on cpu model.
Added Zheng Yan who wrote most of that stuff.
next prev parent reply other threads:[~2012-08-16 7:20 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 [this message]
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
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=1345101585.31459.112.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=asias.hejun@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox