We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
Can someone explain more about this issue, and please provide the fix for this issue.
Hi,
Configuring the memory map to guard against external aborts is a little more involved than using a few MCR instructions, I'm afraid. To cover the memory map, you will need to generate and install a complete set of address translation tables (page tables) and then configure the MMU to use these when determining access rights for memory accesses.
I think you should also note that, as has been said earlier, that this particular erratum is classes as "rare". As far as I can see, the Linux community has not seen fit to modify the Linux kernel to provide any fix or workaround to guard against it happening. Presumably, this is because they have taken the view that, in a correctly configured and functioning kernel, this situation will simply never arise!
Do you have specific reasons for wanting to go further on this one?
Chris