From: Peter Wu <peter@lekensteyn.nl>
To: Gleb Natapov <gleb@kernel.org>
Cc: Venkatesh Srinivas <venkateshs@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Andi Kleen <ak@linux.intel.com>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
kvm@vger.kernel.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: GPF in intel_pmu_lbr_reset() with qemu -cpu host
Date: Sat, 22 Mar 2014 23:00:24 +0100 [thread overview]
Message-ID: <7070151.NcmQcQO4az@al> (raw)
In-Reply-To: <20140322122758.GA4292@minantech.com>
On Saturday 22 March 2014 14:27:59 Gleb Natapov wrote:
> > but now I have a NULL dereference (in rapl_pmu_init). Previously, when
> > `-cpu SandyBridge` was passed to qemu, it would show this:
> >
> > [ 0.016995] Performance Events: unsupported p6 CPU model 42 no PMU driver, software events only.
> >
> > The same NULL pointer deref would be visible (slightly different
> > addresses, but the Code lines are equal). With `-host`, the NULL deref
> > with `-cpu host` contains:
> >
> > [ 0.016445] Performance Events: 16-deep LBR, IvyBridge events, Intel PMU driver.
> >
> > Full dmesg below.
> >
> I am confused. Do you see crash now with -cpu SandyBridge and -cpu host, or -cpu host only?
The RAPL crash is seen with both SandyBridge and host, I mentioned SB
because that environment should be more constant than "host" (which
depends on the CPU you have on, well, the host).
Peter
next prev parent reply other threads:[~2014-03-22 22:00 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 [this message]
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
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=7070151.NcmQcQO4az@al \
--to=peter@lekensteyn.nl \
--cc=ak@linux.intel.com \
--cc=gleb@kernel.org \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=venkateshs@google.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