All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com
Subject: Re: linux 3.13 guest crash with -cpu host
Date: Mon, 3 Feb 2014 15:12:35 +0100	[thread overview]
Message-ID: <20140203141235.GJ8874@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140203140601.GA24944@redhat.com>

On Mon, Feb 03, 2014 at 04:06:01PM +0200, Michael S. Tsirkin wrote:
> On Mon, Feb 03, 2014 at 10:58:28AM -0200, Eduardo Habkost wrote:

> > Where does the "v2 and above have a perf capabilities MSR" claim in the code
> > come from?
> 
> 
> But why doesn't it crash on baremetal?
> Probably baremetal simply returns 0 or something.
> Let me try ..

The claim "v2 and above have FEATURE_PDCM" is in fact true for real
hardware.

If it didn't the rdmsr() would have generated an exception and we'd have
crashed just like your virtual thingy did.

  parent reply	other threads:[~2014-02-03 14:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-02 20:59 linux 3.13 guest crash with -cpu host Michael S. Tsirkin
2014-02-03 12:58 ` Eduardo Habkost
2014-02-03 13:29   ` Peter Zijlstra
2014-02-21 21:14     ` [tip:perf/urgent] perf/x86: Correctly use FEATURE_PDCM tip-bot for Peter Zijlstra
2014-02-03 14:06   ` linux 3.13 guest crash with -cpu host Michael S. Tsirkin
2014-02-03 14:07     ` Paolo Bonzini
2014-02-03 14:42       ` Michael S. Tsirkin
2014-02-03 14:12     ` Peter Zijlstra [this message]
2014-02-03 14:19       ` Paolo Bonzini
2014-02-03 14:26         ` Peter Zijlstra
2014-02-03 14:28           ` Peter Zijlstra
2014-02-03 15:01             ` Paolo Bonzini
2014-02-03 14:45           ` Michael S. Tsirkin

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=20140203141235.GJ8874@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.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.