From: Peter Zijlstra <peterz@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org
Subject: Re: linux 3.13 guest crash with -cpu host
Date: Mon, 3 Feb 2014 15:28:47 +0100 [thread overview]
Message-ID: <20140203142847.GD3229@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140203142642.GK8874@twins.programming.kicks-ass.net>
On Mon, Feb 03, 2014 at 03:26:42PM +0100, Peter Zijlstra wrote:
> On Mon, Feb 03, 2014 at 03:19:18PM +0100, Paolo Bonzini wrote:
> > Il 03/02/2014 15:12, Peter Zijlstra ha scritto:
> > >>> 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.
> >
> > Right, and the virt thingy has no PEBS, so there is no correct value that we
> > could return from the MSR. That's why the CPUID bit is zero.
>
> There's more than PEBS in there, there's also the LBR format (which you
> obviously also don't have)
On that.. LBR is purely model based, what do you guys do with those
MSRs?
next prev parent reply other threads:[~2014-02-03 14:28 UTC|newest]
Thread overview: 12+ 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-03 14:06 ` 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
2014-02-03 14:19 ` Paolo Bonzini
2014-02-03 14:26 ` Peter Zijlstra
2014-02-03 14:28 ` Peter Zijlstra [this message]
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=20140203142847.GD3229@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox