[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7C103AEB-3111-4AE6-9645-CF590388A879@hpe.com>
Date: Tue, 10 May 2022 11:53:57 +0000
From: "Verdun, Jean-Marie" <verdun@....com>
To: Arnd Bergmann <arnd@...db.de>,
"Hawkins, Nick" <nick.hawkins@....com>
CC: Russell King - ARM Linux <linux@...linux.org.uk>,
Will Deacon <will@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Linux ARM <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Joel Stanley <joel@....id.au>
Subject: Re: [PATCH v1] ARM: A9: Add ARM ERRATA 764319 workaround
Hi Arnd,
> Hi Nick,
> This seems a bit more complex than necessary. Can't you just use a custom
> inline asm with an ex_table entry to catch the fault? Have a look at
> __get_user_asm() for an example.
>
> Arnd
We got inspired from debug_reg_hook within the same source file ( ./arch/arm/kernel/hw_breakpoint.c ). We chose that path to keep coherency within the source code. We can implement the same fix by using an ex_table entry, but this will create two different ways at catching unknown instruction within the same source file. Will that be ok ?
vejmarie
Powered by blists - more mailing lists