From: Marc Zyngier <marc.zyngier@arm.com>
To: Will Deacon <will.deacon@arm.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH v4 20/23] arm64: perf: Count EL2 events if the kernel is running in HYP
Date: Mon, 15 Feb 2016 18:23:35 +0000 [thread overview]
Message-ID: <56C217A7.5020105@arm.com> (raw)
In-Reply-To: <20160215172247.GL6298@arm.com>
On 15/02/16 17:22, Will Deacon wrote:
> On Thu, Feb 11, 2016 at 06:40:01PM +0000, Marc Zyngier wrote:
>> When the kernel is running in HYP (with VHE), it is necessary to
>> include EL2 events if the user requests counting kernel or
>> hypervisor events.
>>
>> Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
>> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>> ---
>> arch/arm64/kernel/perf_event.c | 14 ++++++++++----
>> 1 file changed, 10 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
>> index f7ab14c..6013a38 100644
>> --- a/arch/arm64/kernel/perf_event.c
>> +++ b/arch/arm64/kernel/perf_event.c
>> @@ -20,6 +20,7 @@
>> */
>>
>> #include <asm/irq_regs.h>
>> +#include <asm/virt.h>
>>
>> #include <linux/of.h>
>> #include <linux/perf/arm_pmu.h>
>> @@ -693,10 +694,15 @@ static int armv8pmu_set_event_filter(struct hw_perf_event *event,
>> return -EPERM;
>> if (attr->exclude_user)
>> config_base |= ARMV8_EXCLUDE_EL0;
>> - if (attr->exclude_kernel)
>> - config_base |= ARMV8_EXCLUDE_EL1;
>> - if (!attr->exclude_hv)
>> - config_base |= ARMV8_INCLUDE_EL2;
>> + if (is_kernel_in_hyp_mode()) {
>> + if (!attr->exclude_kernel || !attr->exclude_hv)
>> + config_base |= ARMV8_INCLUDE_EL2;
>
> Hmm, so if userspace sets exclude_kernel but not exclude_user and
> exclude_hv, what should we do? I'm slightly tempted to reject the
> filter with -EINVAL...
I was angling for the minimum level of surprise for the user, but
I guess that the results are going to be troubling anyway.
How about something like this on top:
diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
index 6013a38..8c00ed4 100644
--- a/arch/arm64/kernel/perf_event.c
+++ b/arch/arm64/kernel/perf_event.c
@@ -695,7 +695,10 @@ static int armv8pmu_set_event_filter(struct hw_perf_event *event,
if (attr->exclude_user)
config_base |= ARMV8_EXCLUDE_EL0;
if (is_kernel_in_hyp_mode()) {
- if (!attr->exclude_kernel || !attr->exclude_hv)
+ /* Demand that kernel and hv are consistent */
+ if (attr->exclude_kernel != attr->exclude_hv)
+ return -EINVAL;
+ if (!attr->exclude_hv)
config_base |= ARMV8_INCLUDE_EL2;
} else {
if (attr->exclude_kernel)
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 20/23] arm64: perf: Count EL2 events if the kernel is running in HYP
Date: Mon, 15 Feb 2016 18:23:35 +0000 [thread overview]
Message-ID: <56C217A7.5020105@arm.com> (raw)
In-Reply-To: <20160215172247.GL6298@arm.com>
On 15/02/16 17:22, Will Deacon wrote:
> On Thu, Feb 11, 2016 at 06:40:01PM +0000, Marc Zyngier wrote:
>> When the kernel is running in HYP (with VHE), it is necessary to
>> include EL2 events if the user requests counting kernel or
>> hypervisor events.
>>
>> Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
>> Acked-by: Catalin Marinas <catalin.marinas@arm.com>
>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>> ---
>> arch/arm64/kernel/perf_event.c | 14 ++++++++++----
>> 1 file changed, 10 insertions(+), 4 deletions(-)
>>
>> diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
>> index f7ab14c..6013a38 100644
>> --- a/arch/arm64/kernel/perf_event.c
>> +++ b/arch/arm64/kernel/perf_event.c
>> @@ -20,6 +20,7 @@
>> */
>>
>> #include <asm/irq_regs.h>
>> +#include <asm/virt.h>
>>
>> #include <linux/of.h>
>> #include <linux/perf/arm_pmu.h>
>> @@ -693,10 +694,15 @@ static int armv8pmu_set_event_filter(struct hw_perf_event *event,
>> return -EPERM;
>> if (attr->exclude_user)
>> config_base |= ARMV8_EXCLUDE_EL0;
>> - if (attr->exclude_kernel)
>> - config_base |= ARMV8_EXCLUDE_EL1;
>> - if (!attr->exclude_hv)
>> - config_base |= ARMV8_INCLUDE_EL2;
>> + if (is_kernel_in_hyp_mode()) {
>> + if (!attr->exclude_kernel || !attr->exclude_hv)
>> + config_base |= ARMV8_INCLUDE_EL2;
>
> Hmm, so if userspace sets exclude_kernel but not exclude_user and
> exclude_hv, what should we do? I'm slightly tempted to reject the
> filter with -EINVAL...
I was angling for the minimum level of surprise for the user, but
I guess that the results are going to be troubling anyway.
How about something like this on top:
diff --git a/arch/arm64/kernel/perf_event.c b/arch/arm64/kernel/perf_event.c
index 6013a38..8c00ed4 100644
--- a/arch/arm64/kernel/perf_event.c
+++ b/arch/arm64/kernel/perf_event.c
@@ -695,7 +695,10 @@ static int armv8pmu_set_event_filter(struct hw_perf_event *event,
if (attr->exclude_user)
config_base |= ARMV8_EXCLUDE_EL0;
if (is_kernel_in_hyp_mode()) {
- if (!attr->exclude_kernel || !attr->exclude_hv)
+ /* Demand that kernel and hv are consistent */
+ if (attr->exclude_kernel != attr->exclude_hv)
+ return -EINVAL;
+ if (!attr->exclude_hv)
config_base |= ARMV8_INCLUDE_EL2;
} else {
if (attr->exclude_kernel)
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2016-02-15 18:23 UTC|newest]
Thread overview: 119+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-11 18:39 [PATCH v4 00/23] arm64: Virtualization Host Extension support Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 01/23] arm/arm64: KVM: Add hook for C-based stage2 init Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 02/23] arm64: KVM: Switch to " Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 03/23] arm/arm64: Add new is_kernel_in_hyp_mode predicate Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 04/23] arm64: Allow the arch timer to use the HYP timer Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 05/23] arm64: Add ARM64_HAS_VIRT_HOST_EXTN feature Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-15 16:10 ` Will Deacon
2016-02-15 16:10 ` Will Deacon
2016-02-11 18:39 ` [PATCH v4 06/23] arm64: KVM: Skip HYP setup when already running in HYP Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 07/23] arm64: KVM: VHE: Patch out use of HVC Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 08/23] arm64: KVM: VHE: Patch out kern_hyp_va Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 09/23] arm64: KVM: VHE: Introduce unified system register accessors Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 10/23] arm64: KVM: VHE: Differenciate host/guest sysreg save/restore Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 11/23] arm64: KVM: VHE: Split save/restore of registers shared between guest and host Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 12/23] arm64: KVM: VHE: Use unified system register accessors Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 13/23] arm64: KVM: VHE: Enable minimal sysreg save/restore Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 14/23] arm64: KVM: VHE: Make __fpsimd_enabled VHE aware Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 15/23] arm64: KVM: VHE: Implement VHE activate/deactivate_traps Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 16/23] arm64: KVM: VHE: Use unified sysreg accessors for timer Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 17/23] arm64: KVM: VHE: Add fpsimd enabling on guest access Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` [PATCH v4 18/23] arm64: KVM: VHE: Add alternative panic handling Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:39 ` Marc Zyngier
2016-02-11 18:40 ` [PATCH v4 19/23] arm64: KVM: Move most of the fault decoding to C Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` [PATCH v4 20/23] arm64: perf: Count EL2 events if the kernel is running in HYP Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-15 17:22 ` Will Deacon
2016-02-15 17:22 ` Will Deacon
2016-02-15 17:22 ` Will Deacon
2016-02-15 18:23 ` Marc Zyngier [this message]
2016-02-15 18:23 ` Marc Zyngier
2016-02-15 18:27 ` Will Deacon
2016-02-15 18:27 ` Will Deacon
2016-02-15 18:27 ` Will Deacon
2016-02-11 18:40 ` [PATCH v4 21/23] arm64: hw_breakpoint: Allow EL2 breakpoints if " Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-15 10:22 ` Catalin Marinas
2016-02-15 10:22 ` Catalin Marinas
2016-02-15 17:46 ` Will Deacon
2016-02-15 17:46 ` Will Deacon
2016-02-15 19:07 ` Will Deacon
2016-02-15 19:07 ` Will Deacon
2016-02-15 19:07 ` Will Deacon
2016-02-16 9:55 ` Marc Zyngier
2016-02-16 9:55 ` Marc Zyngier
2016-02-16 9:55 ` Marc Zyngier
2016-02-17 17:57 ` [PATCH v4.1] arm64: perf: Count EL2 events if the kernel is " Marc Zyngier
2016-02-17 17:57 ` Marc Zyngier
2016-02-19 14:30 ` Will Deacon
2016-02-19 14:30 ` Will Deacon
2016-02-19 14:30 ` Will Deacon
2016-02-11 18:40 ` [PATCH v4 22/23] arm64: VHE: Add support for running Linux in EL2 mode Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-17 17:58 ` [PATCH v4.1] arm64: hw_breakpoint: Allow EL2 breakpoints if running in HYP Marc Zyngier
2016-02-17 17:58 ` Marc Zyngier
2016-02-17 17:58 ` Marc Zyngier
2016-02-19 14:30 ` Will Deacon
2016-02-19 14:30 ` Will Deacon
2016-02-19 14:30 ` Will Deacon
2016-02-11 18:40 ` [PATCH v4 23/23] arm64: Panic when VHE and non VHE CPUs coexist Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-11 18:40 ` Marc Zyngier
2016-02-15 17:26 ` Will Deacon
2016-02-15 17:26 ` Will Deacon
2016-02-15 18:14 ` Marc Zyngier
2016-02-15 18:14 ` Marc Zyngier
2016-02-15 18:14 ` Marc Zyngier
2016-02-11 19:07 ` [PATCH v4 00/23] arm64: Virtualization Host Extension support Christoffer Dall
2016-02-11 19:07 ` Christoffer Dall
2016-02-11 19:10 ` Marc Zyngier
2016-02-11 19:10 ` Marc Zyngier
2016-02-11 19:10 ` Marc Zyngier
2016-02-15 10:23 ` Catalin Marinas
2016-02-15 10:23 ` Catalin Marinas
2016-02-15 10:34 ` Marc Zyngier
2016-02-15 10:34 ` Marc Zyngier
2016-02-15 10:34 ` Marc Zyngier
2016-02-29 17:43 ` Alex Bennée
2016-02-29 17:43 ` Alex Bennée
2016-02-29 17:43 ` Alex Bennée
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=56C217A7.5020105@arm.com \
--to=marc.zyngier@arm.com \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=will.deacon@arm.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.