public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Andre Przywara <andre.przywara@amd.com>
Cc: mingo@elte.hu, konrad.wilk@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/perf: Fix virtualization sanity check
Date: Tue, 09 Oct 2012 17:41:44 +0200	[thread overview]
Message-ID: <1349797304.7880.70.camel@twins> (raw)
In-Reply-To: <1349797115-28346-1-git-send-email-andre.przywara@amd.com>

On Tue, 2012-10-09 at 17:38 +0200, Andre Przywara wrote:
> First you need an AMD family 10h/12h CPU. These do not reset the
> PERF_CTR registers on a reboot.
> Now you boot bare metal Linux, which goes successfully through this
> check, but leaves the magic value of 0xabcd in the register. You
> don't use the performance counters, but do a reboot (warm reset).
> Then you choose to boot Xen. The check will be triggered with a
> recent Linux kernel as Dom0 again, trying to write 0xabcd into the
> MSR. Xen silently drops the write (expected), but the subsequent read
> will return the value in the register, which just happens to be the
> expected magic value. Thus the test misleadingly succeeds, leaving
> the kernel in the belief that the PMU is available 

Wow.. ! that's uhm.. shees!

Bit weird of Xen to trap writes but not reads of MSRs though.

The patchs looks fine though, thanks!

  parent reply	other threads:[~2012-10-09 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-09 15:38 [PATCH] x86/perf: Fix virtualization sanity check Andre Przywara
2012-10-09 15:38 ` Andre Przywara
2012-10-24  9:36   ` [tip:perf/core] " tip-bot for Andre Przywara
2012-10-09 15:41 ` Peter Zijlstra [this message]
2012-10-09 15:51 ` [PATCH] " Konrad Rzeszutek Wilk
2012-10-09 22:32   ` Andre Przywara
2012-10-10 12:52     ` Konrad Rzeszutek Wilk

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=1349797304.7880.70.camel@twins \
    --to=peterz@infradead.org \
    --cc=andre.przywara@amd.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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