From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] arm64: Emulate CP15 Barrier instructions
Date: Tue, 26 Aug 2014 14:16:30 +0100 [thread overview]
Message-ID: <20140826131630.GP23445@arm.com> (raw)
In-Reply-To: <1409048930-21598-7-git-send-email-punit.agrawal@arm.com>
On Tue, Aug 26, 2014 at 11:28:50AM +0100, Punit Agrawal wrote:
> The CP15 barrier instructions (CP15ISB, CP15DSB and CP15DMB) are
> deprecated in the ARMv7 architecture, superseded by ISB, DSB and DMB
> instructions respectively. Some implementations may provide support
> for these instructions which can then be enabled by setting the
> CP15BEN bit in the SCTLR in ARMv7 or SCTLR_EL1 in ARMv8. If not
> enabled, the encodings for these instructions become undefined.
>
> To support legacy software that uses these instructions, this patch
> emulates the barrier instructions by installing an undefined
> instruction handler. The patch also adds a debugfs entry to track
> the occurrence of the deprecated barrier instructions. It is possible
> to runtime disable them from debugfs.
[...]
> diff --git a/arch/arm64/kernel/v7_obsolete.c b/arch/arm64/kernel/v7_obsolete.c
> index e9427cb..ed77889 100644
> --- a/arch/arm64/kernel/v7_obsolete.c
> +++ b/arch/arm64/kernel/v7_obsolete.c
> @@ -227,6 +227,94 @@ static void __init swp_emulation_init(void)
> pr_notice("Registered SWP/SWPB emulation handler\n");
> }
>
> +static atomic_t cp15_barrier_count;
> +static u32 cp15_barrier_enabled = 1;
Stupid question, but how this variable get updated?
> +
> +static int cp15barrier_handler(struct pt_regs *regs, u32 instr)
> +{
> + if (!cp15_barrier_enabled)
> + return -EFAULT;
> +
> + perf_sw_event(PERF_COUNT_SW_EMULATION_FAULTS, 1, regs, regs->pc);
> +
> + switch (arm_check_condition(instr, regs->pstate)) {
> + case ARM_OPCODE_CONDTEST_PASS:
> + break;
> + case ARM_OPCODE_CONDTEST_FAIL:
> + /* Condition failed - return to next instruction */
> + goto ret;
> + case ARM_OPCODE_CONDTEST_UNCOND:
> + /* If unconditional encoding - not a barrier instruction */
> + return -EFAULT;
> + default:
> + return -EINVAL;
> + }
> +
> + switch(aarch32_insn_mcr_extract_crm(instr)) {
> + case 10:
> + /*
> + * dmb - mcr p15, 0, Rt, c7, c10, 5
> + * dsb - mcr p15, 0, Rt, c7, c10, 4
> + */
> + if (aarch32_insn_mcr_extract_opc2(instr) == 5)
> + dmb();
> + else
> + dsb();
It would be cleaner to check for the value 4 here.
> + break;
> + case 5:
> + /*
> + * isb - mcr p15, 0, Rt, c7, c5, 4
> + */
> + isb();
You don't need this isb() -- it is implicit in the exception return. A
comment to that effect will suffice.
Will
next prev parent reply other threads:[~2014-08-26 13:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 10:28 [PATCH 0/6] Legacy instruction emulation for arm64 Punit Agrawal
2014-08-26 10:28 ` [PATCH 1/6] arm: Fix in-correct barrier usage in SWP{B} emulation Punit Agrawal
2014-08-26 13:04 ` Will Deacon
2014-08-27 16:40 ` Catalin Marinas
2014-08-27 17:05 ` Punit Agrawal
2014-08-26 10:28 ` [PATCH 2/6] arm64: Create arch debugfs directory Punit Agrawal
2014-08-26 10:28 ` [PATCH 3/6] arm64: Add support for hooks to handle undefined instructions Punit Agrawal
2014-08-26 13:13 ` Will Deacon
2014-08-26 14:21 ` Ard Biesheuvel
2014-08-26 14:30 ` Will Deacon
2014-08-27 16:47 ` Catalin Marinas
2014-08-27 16:51 ` Will Deacon
2014-08-26 14:56 ` Punit Agrawal
2014-08-26 18:14 ` Will Deacon
2014-08-27 16:58 ` Catalin Marinas
2014-08-26 10:28 ` [PATCH 4/6] arm64: Add AArch32 instruction set condition code checks Punit Agrawal
2014-08-26 10:28 ` [PATCH 5/6] arm64: Port SWP/SWPB emulation support from arm Punit Agrawal
2014-08-26 11:32 ` Arnd Bergmann
2014-08-26 12:25 ` Will Deacon
2014-08-26 13:26 ` Arnd Bergmann
2014-08-26 13:56 ` Will Deacon
2014-08-27 17:35 ` Punit Agrawal
2014-08-27 18:30 ` Arnd Bergmann
2014-08-28 10:21 ` Punit Agrawal
2014-08-27 17:29 ` Catalin Marinas
2014-08-26 10:28 ` [PATCH 6/6] arm64: Emulate CP15 Barrier instructions Punit Agrawal
2014-08-26 13:16 ` Will Deacon [this message]
2014-08-27 17:40 ` Catalin Marinas
2014-08-28 9:34 ` Punit Agrawal
2014-08-28 9:42 ` Catalin Marinas
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=20140826131630.GP23445@arm.com \
--to=will.deacon@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 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).