From: Andrew Jones <drjones@redhat.com>
To: Wei Huang <wei@redhat.com>
Cc: qemu-arm@nongnu.org, peter.maydell@linaro.org,
qemu-devel@nongnu.org, abologna@redhat.com,
shannon.zhao@linaro.org
Subject: Re: [Qemu-devel] [PATCH V7 0/2] Add option to configure guest vPMU
Date: Mon, 24 Oct 2016 10:49:20 +0200 [thread overview]
Message-ID: <20161024084920.5qrrwa3wfdyr5kn5@hawk.localdomain> (raw)
In-Reply-To: <1477086782-10479-1-git-send-email-wei@redhat.com>
On Fri, Oct 21, 2016 at 05:53:00PM -0400, Wei Huang wrote:
> This patchset adds a pmu=[on/off] option to enable/disable vPMU support
> for guest VM. There are several reasons to justify this option. First,
> vPMU can be problematic for cross-migration between different SoC as perf
> counters are architecture-dependent. It is more flexible to have an option
> to turn it on/off. Secondly this option matches the "pmu" option as
> supported in libvirt. To make sure backward compatible, a PMU-related
> property is added to mach-virt machine types.
>
> The following are testing results with this patchset:
> CONFIG (qemu-system-aarch64) vPMU WARNING
> -M virt-2.8/virt,accel=kvm -cpu host YES NO
> -M virt-2.8/virt,accel=kvm -cpu host,pmu=off NO NO
> -M virt-2.8/virt,accel=kvm -cpu host,pmu=on YES NO
> -M virt-2.7,accel=kvm -cpu host YES NO
> -M virt-2.7,accel=kvm -cpu host,pmu=off NO NO
> -M virt-2.7,accel=kvm -cpu host,pmu=on YES NO
> -M virt-2.6,accel=kvm -cpu host NO NO
> -M virt-2.6,accel=kvm -cpu host,pmu=off NO NO
> -M virt-2.6,accel=kvm -cpu host,pmu=on NO NO
>
> -M virt-2.8/virt,accel=tcg -cpu cortex-a57 NO NO
> -M virt-2.8/virt,accel=tcg -cpu cortex-a57,pmu=off NO "No PMU property"
> -M virt-2.8/virt,accel=tcg -cpu cortex-a57,pmu=on NO "No PMU property"
> -M virt-2.7,accel=tcg -cpu cortex-a57 NO NO
> -M virt-2.7,accel=tcg -cpu cortex-a57,pmu=off NO "No PMU property"
> -M virt-2.7,accel=tcg -cpu cortex-a57,pmu=on NO "No PMU property"
> -M virt-2.6,accel=tcg -cpu cortex-a57 NO NO
> -M virt-2.6,accel=tcg -cpu cortex-a57,pmu=off NO "No PMU property"
> -M virt-2.6,accel=tcg -cpu cortex-a57,pmu=on NO "No PMU property"
>
> -M virt-2.8/virt,accel=tcg -cpu cortex-a15 NO NO
> -M virt-2.8/virt,accel=tcg -cpu cortex-a15,pmu=off NO "No PMU property"
> -M virt-2.8/virt,accel=tcg -cpu cortex-a15,pmu=on NO "No PMU property"
> -M virt-2.7,accel=tcg -cpu cortex-a15 NO NO
> -M virt-2.7,accel=tcg -cpu cortex-a15,pmu=off NO "No PMU property"
> -M virt-2.7,accel=tcg -cpu cortex-a15,pmu=on NO "No PMU property"
> -M virt-2.6,accel=tcg -cpu cortex-a15 NO NO
> -M virt-2.6,accel=tcg -cpu cortex-a15,pmu=off NO "No PMU property"
> -M virt-2.6,accel=tcg -cpu cortex-a15,pmu=on NO "No PMU property"
>
> * "No PMU property" msg, e.g.
> can't apply global cortex-a15-arm-cpu.pmu=off: Property '.pmu' not found
>
> V6->V7:
> * change has_pmu variable type from OnOffAuto to Boolean
> * only add "pmu" property to CPU under kvm mode, default ON
Hmm, if we don't allow the property with TCG then switching a guest from
KVM to TCG will require more than just an accelerator switch. That's a
bit annoying and I think we'd have to teach it to libvirt too. I'd prefer
-M virt-2.8,accel=tcg -cpu cortex-a57 NO NO
-M virt-2.8,accel=tcg -cpu cortex-a57,pmu=off NO NO
-M virt-2.8,accel=tcg -cpu cortex-a57,pmu=on NO "Warning: PMU not
yet supported with TCG" (or something)
> * set no_pmu=true for machvirt-2.6
>
> V5->V6:
> * adapt patches for new machine type 2.8
>
> V4->V5:
> * remove comment change for has_pmu
> * remove warning msg when pmu_default_on=TRUE && has_pmu=AUTO && tcg=TRUE
>
> V3->V4:
> * change has_pmu from Boolean to OnOffAuto to handle different cases
> * "pmu" property is re-defined as DEFINE_PROP_ON_OFF_AUTO
>
> V2->V3:
> * revise patch 1 commit msg and if-else statement (Drew)
> * move property field into VirtMachineClass (Drew)
>
> V1->V2:
> * keep the original field name as "has_pmu"
> * add a warning message when PMU is turned on without KVM
> * use the feature bit to check PMU availability, instead of using has_pmu
> * add PMU compat support to mach-virt machine type
>
> RFC->V1:
> * set default pmu=off
> * change struct ARMCPU field name "has_pmu" ==> "has_host_pmu"
> * like el3, add a new feature ARM_FEATURE_HOST_PMU
> * "pmu" property becomes CPU dependent. Only cortex-a53/cortex-a57/host
> running on kvm supports this option.
>
> Thanks,
> -Wei
>
> Wei Huang (2):
> arm64: Add an option to turn on/off vPMU support
> arm: virt: add PMU property to mach-virt machine type
>
> hw/arm/virt-acpi-build.c | 2 +-
> hw/arm/virt.c | 9 ++++++++-
> target-arm/cpu.c | 14 ++++++++++++++
> target-arm/cpu.h | 1 +
> target-arm/cpu64.c | 2 ++
> target-arm/kvm64.c | 17 ++++++++++++++---
> 6 files changed, 40 insertions(+), 5 deletions(-)
>
> --
> 1.8.3.1
>
>
next prev parent reply other threads:[~2016-10-24 8:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-21 21:53 [Qemu-devel] [PATCH V7 0/2] Add option to configure guest vPMU Wei Huang
2016-10-21 21:53 ` [Qemu-devel] [PATCH V7 1/2] arm: Add an option to turn on/off vPMU support Wei Huang
2016-10-27 14:24 ` Peter Maydell
2016-10-21 21:53 ` [Qemu-devel] [PATCH V7 2/2] arm: virt: add PMU property to mach-virt machine type Wei Huang
2016-10-24 9:13 ` Andrew Jones
2016-10-24 8:49 ` Andrew Jones [this message]
2016-10-25 4:39 ` [Qemu-devel] [PATCH V7 0/2] Add option to configure guest vPMU Wei Huang
2016-10-25 7:33 ` Andrew Jones
2016-10-25 15:26 ` Peter Maydell
2016-10-25 15:59 ` Peter Maydell
2016-10-25 17:16 ` Wei Huang
2016-10-25 16:55 ` Wei Huang
2016-10-25 17:56 ` Andrew Jones
2016-10-25 18:50 ` Wei Huang
2016-10-26 6:54 ` Andrew Jones
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=20161024084920.5qrrwa3wfdyr5kn5@hawk.localdomain \
--to=drjones@redhat.com \
--cc=abologna@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).