public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter Wu <peter@lekensteyn.nl>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: GPF in intel_pmu_lbr_reset() with qemu -cpu host
Date: Fri, 21 Mar 2014 17:26:17 -0700	[thread overview]
Message-ID: <532CD8A9.5080603@zytor.com> (raw)
In-Reply-To: <20140322002244.GP22728@two.firstfloor.org>

On 03/21/2014 05:22 PM, Andi Kleen wrote:
>> Actually, Ingo, Borislav and I have been discussing making rdmsr_safe()
>> more of the default, especially for things like this where the error
>> handling is obvious (doesn't work?  Disable the PMU.)
> 
> That would be completely wrong. KVM has a full architectural perfmon PMU,
> just no model specific extensions like LBR.
> 

s/PMU/PMU extension in question/

	-hpa



  reply	other threads:[~2014-03-22  0:27 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:42 GPF in intel_pmu_lbr_reset() with qemu -cpu host Peter Wu
2014-03-21 17:46 ` Peter Wu
2014-03-21 19:04   ` Venkatesh Srinivas
2014-03-21 19:09     ` H. Peter Anvin
2014-03-22  7:54       ` Paolo Bonzini
2014-03-22  8:50     ` Gleb Natapov
2014-03-22 10:05       ` Peter Wu
2014-03-22 12:27         ` Gleb Natapov
2014-03-22 21:46           ` H. Peter Anvin
2014-03-22 22:00           ` Peter Wu
2014-03-26  7:23             ` Wu, Feng
2014-03-26  9:38               ` Paolo Bonzini
2014-03-21 19:29 ` Andi Kleen
2014-03-21 20:46   ` H. Peter Anvin
2014-03-21 21:37     ` Andi Kleen
2014-03-21 21:41       ` H. Peter Anvin
2014-03-21 21:48         ` Andi Kleen
2014-03-21 21:55           ` H. Peter Anvin
2014-03-22  0:22             ` Andi Kleen
2014-03-22  0:26               ` H. Peter Anvin [this message]
2014-03-22  0:30                 ` Andi Kleen
2014-03-22  0:34                   ` H. Peter Anvin
2014-03-22 10:01                     ` Borislav Petkov

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=532CD8A9.5080603@zytor.com \
    --to=hpa@zytor.com \
    --cc=andi@firstfloor.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peter@lekensteyn.nl \
    --cc=peterz@infradead.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