From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/9] arm64: KVM: rename pm_fake handler to trap_wi_raz
Date: Wed, 07 May 2014 16:42:06 +0100 [thread overview]
Message-ID: <536A544E.4000101@arm.com> (raw)
In-Reply-To: <CAFEAcA-v4ek1+JDKDfE3n+HSigutqfv1aU=VdxTtxFAd25S6fg@mail.gmail.com>
On 07/05/14 16:34, Peter Maydell wrote:
> On 7 May 2014 16:20, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> pm_fake doesn't quite describe what the handler does (ignoring writes
>> and returning 0 for reads).
>>
>> As we're about to use it (a lot) in a different context, rename it
>> with a (admitedly cryptic) name that make sense for all users.
>
>> -/*
>> - * We could trap ID_DFR0 and tell the guest we don't support performance
>> - * monitoring. Unfortunately the patch to make the kernel check ID_DFR0 was
>> - * NAKed, so it will read the PMCR anyway.
>> - *
>> - * Therefore we tell the guest we have 0 counters. Unfortunately, we
>> - * must always support PMCCNTR (the cycle counter): we just RAZ/WI for
>> - * all PM registers, which doesn't crash the guest kernel at least.
>> - */
>> -static bool pm_fake(struct kvm_vcpu *vcpu,
>> - const struct sys_reg_params *p,
>> - const struct sys_reg_desc *r)
>> +static bool trap_wi_raz(struct kvm_vcpu *vcpu,
>> + const struct sys_reg_params *p,
>> + const struct sys_reg_desc *r)
>
> The standard term for this is "RAZ/WI", not "WI/RAZ", so
> why not "trap_raz_wi" ?
Good point. I'll update it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <marc.zyngier@arm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
kvm-devel <kvm@vger.kernel.org>,
Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Ian Campbell <ian.campbell@citrix.com>
Subject: Re: [PATCH 1/9] arm64: KVM: rename pm_fake handler to trap_wi_raz
Date: Wed, 07 May 2014 16:42:06 +0100 [thread overview]
Message-ID: <536A544E.4000101@arm.com> (raw)
In-Reply-To: <CAFEAcA-v4ek1+JDKDfE3n+HSigutqfv1aU=VdxTtxFAd25S6fg@mail.gmail.com>
On 07/05/14 16:34, Peter Maydell wrote:
> On 7 May 2014 16:20, Marc Zyngier <marc.zyngier@arm.com> wrote:
>> pm_fake doesn't quite describe what the handler does (ignoring writes
>> and returning 0 for reads).
>>
>> As we're about to use it (a lot) in a different context, rename it
>> with a (admitedly cryptic) name that make sense for all users.
>
>> -/*
>> - * We could trap ID_DFR0 and tell the guest we don't support performance
>> - * monitoring. Unfortunately the patch to make the kernel check ID_DFR0 was
>> - * NAKed, so it will read the PMCR anyway.
>> - *
>> - * Therefore we tell the guest we have 0 counters. Unfortunately, we
>> - * must always support PMCCNTR (the cycle counter): we just RAZ/WI for
>> - * all PM registers, which doesn't crash the guest kernel at least.
>> - */
>> -static bool pm_fake(struct kvm_vcpu *vcpu,
>> - const struct sys_reg_params *p,
>> - const struct sys_reg_desc *r)
>> +static bool trap_wi_raz(struct kvm_vcpu *vcpu,
>> + const struct sys_reg_params *p,
>> + const struct sys_reg_desc *r)
>
> The standard term for this is "RAZ/WI", not "WI/RAZ", so
> why not "trap_raz_wi" ?
Good point. I'll update it.
Thanks,
M.
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2014-05-07 15:42 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 15:20 [PATCH 0/9] arm64: KVM: debug infrastructure support Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-07 15:20 ` [PATCH 1/9] arm64: KVM: rename pm_fake handler to trap_wi_raz Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-07 15:34 ` Peter Maydell
2014-05-07 15:34 ` Peter Maydell
2014-05-07 15:42 ` Marc Zyngier [this message]
2014-05-07 15:42 ` Marc Zyngier
2014-05-19 8:43 ` Anup Patel
2014-05-19 8:43 ` Anup Patel
2014-05-07 15:20 ` [PATCH 2/9] arm64: move DBG_MDSCR_* to asm/debug-monitors.h Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-07 17:14 ` Will Deacon
2014-05-07 17:14 ` Will Deacon
2014-05-07 15:20 ` [PATCH 3/9] arm64: KVM: add trap handlers for AArch64 debug registers Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:27 ` Anup Patel
2014-05-19 8:27 ` Anup Patel
2014-05-07 15:20 ` [PATCH 4/9] arm64: KVM: common infrastructure for handling AArch32 CP14/CP15 Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:29 ` Anup Patel
2014-05-19 8:29 ` Anup Patel
2014-05-07 15:20 ` [PATCH 5/9] arm64: KVM: use separate tables for AArch32 32 and 64bit traps Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:29 ` Anup Patel
2014-05-19 8:29 ` Anup Patel
2014-05-07 15:20 ` [PATCH 6/9] arm64: KVM: check ordering of all system register tables Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:31 ` Anup Patel
2014-05-19 8:31 ` Anup Patel
2014-05-07 15:20 ` [PATCH 7/9] arm64: KVM: add trap handlers for AArch32 debug registers Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:33 ` Anup Patel
2014-05-19 8:33 ` Anup Patel
2014-05-07 15:20 ` [PATCH 8/9] arm64: KVM: implement lazy world switch for " Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:38 ` Anup Patel
2014-05-19 8:38 ` Anup Patel
2014-05-19 16:01 ` Marc Zyngier
2014-05-19 16:01 ` Marc Zyngier
2014-05-07 15:20 ` [PATCH 9/9] arm64: KVM: enable trapping of all " Marc Zyngier
2014-05-07 15:20 ` Marc Zyngier
2014-05-19 8:40 ` Anup Patel
2014-05-19 8:40 ` Anup Patel
2014-05-07 15:42 ` [PATCH 0/9] arm64: KVM: debug infrastructure support Peter Maydell
2014-05-07 15:42 ` Peter Maydell
2014-05-07 15:57 ` Marc Zyngier
2014-05-07 15:57 ` Marc Zyngier
2014-05-19 9:05 ` Anup Patel
2014-05-19 9:05 ` Anup Patel
2014-05-19 9:28 ` Marc Zyngier
2014-05-19 9:28 ` Marc Zyngier
2014-05-19 9:35 ` Anup Patel
2014-05-19 9:35 ` Anup Patel
2014-05-19 12:22 ` Marc Zyngier
2014-05-19 12:22 ` Marc Zyngier
2014-05-19 12:32 ` Peter Maydell
2014-05-19 12:32 ` Peter Maydell
2014-05-19 12:59 ` Marc Zyngier
2014-05-19 12:59 ` Marc Zyngier
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=536A544E.4000101@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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.