lkml.org 
[lkml]   [2022]   [Mar]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [PATCH] [v1] arch: arm: configs: gxp_defconfig
Date
Hi,

> Unfortunately that is not possible at the moment, as this is a 'bool'
> option rather than
> a 'tristate'. I don't know if it might be possible to change that, but
> this is probably
> done for a good reason.

You are right.

> I think it should be possible to detect this erratum at runtime, especially now
> that we understand what the hardware issue is.

> We should probably add a CONFIG_ARM_ERRATA_764319 Kconfig
> option that controls whether a workaround is enabled or not. One
> way that I think this can be handled is to have a custom inline asm
> for the trapping register CP14 accesses, using a __ex_table fixup,
> similar to what we do for trapping user space memory access.

I like this idea. Let me try to implement it and propose something.
Thanks for the feedbacks.

> Another option would be to detect affected systems by the CPU
> revision register or from some DT properties.

ARM might be able to provide that. Let me ask them

vejmarie

\
 
 \ /
  Last update: 2022-03-23 02:03    [W:0.068 / U:0.440 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site