From: Andrea Bolognani <abologna@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Andrew Jones <drjones@redhat.com>, Wei Huang <wei@redhat.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Shannon Zhao <shannon.zhao@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RFC 1/1] arm64: add an option to turn on/off vpmu support
Date: Mon, 01 Aug 2016 16:55:01 +0200 [thread overview]
Message-ID: <1470063301.3971.15.camel@redhat.com> (raw)
In-Reply-To: <CAFEAcA97p9GFrp+tX3pwqeVaSxjxVwuPvCAgZt5aYd_Yk+mGnA@mail.gmail.com>
On Mon, 2016-08-01 at 14:32 +0100, Peter Maydell wrote:
> > Wouldn't that mean that you'd be unable to use
> >
> > -cpu foo,pmu=off
> >
> > if CPU model 'foo' doesn't support a PMU? I'd expect that
> > to work.
>
> The current precedent (has_el3) doesn't work like that: if
> foo isn't a CPU which can support EL3 then the property doesn't
> exist, and it's an error to try to set it.
Doesn't look like the pmu option works like that on x86,
though, unless I'm missing something.
I have a guest running with
-cpu pentium,pmu=on
and I can't see hardware perf events from inside the guest,
eg. dmesg reports
Performance Events: no PMU driver, software events only.
and perf tells me
<not supported> instructions
<not supported> branches
...
I'm not sure whether that's because the PMU is being
emulated but the kernel doesn't have a driver for it, or
whether it's not being emulated at all. Any way to find
out?
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2016-08-01 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 16:38 [Qemu-devel] [PATCH RFC 1/1] arm64: add an option to turn on/off vpmu support Wei Huang
2016-07-29 0:59 ` Shannon Zhao
2016-07-29 6:54 ` Andrew Jones
2016-07-29 15:07 ` Wei Huang
2016-07-29 15:29 ` Peter Maydell
2016-08-01 12:04 ` Andrea Bolognani
2016-08-01 13:08 ` Andrew Jones
2016-08-01 13:16 ` Peter Maydell
2016-08-01 13:26 ` Andrea Bolognani
2016-08-01 13:32 ` Peter Maydell
2016-08-01 14:55 ` Andrea Bolognani [this message]
2016-08-13 6:06 ` Wei Huang
2016-08-15 9:24 ` Andrea Bolognani
2016-07-29 7:57 ` Peter Maydell
2016-07-29 15:08 ` Wei Huang
2016-07-29 15:25 ` Peter Maydell
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=1470063301.3971.15.camel@redhat.com \
--to=abologna@redhat.com \
--cc=drjones@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=shannon.zhao@linaro.org \
--cc=wei@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;
as well as URLs for NNTP newsgroup(s).