From: Avi Kivity <avi@redhat.com>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Pekka Enberg <penberg@kernel.org>,
"Yan, Zheng" <zheng.z.yan@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Sasha Levin <levinsasha928@gmail.com>,
Asias He <asias.hejun@gmail.com>, Ingo Molnar <mingo@elte.hu>,
KVM General <kvm@vger.kernel.org>
Subject: Re: perf uncore & lkvm woes
Date: Thu, 16 Aug 2012 11:45:52 +0300 [thread overview]
Message-ID: <502CB340.7080205@redhat.com> (raw)
In-Reply-To: <20120816074606.GC32081@moon>
On 08/16/2012 10:46 AM, Cyrill Gorcunov wrote:
> On Thu, Aug 16, 2012 at 10:41:53AM +0300, Pekka Enberg wrote:
>> On 08/16/2012 03:19 PM, Peter Zijlstra wrote:
>> >> 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.
>>
>> On Thu, Aug 16, 2012 at 10:38 AM, Yan, Zheng
>> <zheng.z.yan@linux.intel.com> wrote:
>> > The Intel uncore doc does not specify how to check if uncore exist.
>> > How about disabling uncore on virtualized CPU?
>>
>> (CC'ing Avi.)
>
> Why not simply add bootline option for that? Would it be acceptible?
>
Most users just install a distro, they don't mess with kernel command lines.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-08-16 8:46 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 [this message]
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=502CB340.7080205@redhat.com \
--to=avi@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=asias.hejun@gmail.com \
--cc=gorcunov@openvz.org \
--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;
as well as URLs for NNTP newsgroup(s).