Joakim Tjernlund wrote:
Scott Wood <scottw...@freescale.com> wrote on 10/11/2009 23:02:10:
Joakim Tjernlund wrote:
It wasn't the CPU15 workaround that I was worried about taking down the
pinning -- but rather the CPU15 bug itself causing bad code to be
executed inside the pinned kernel mapping.
Oh, but then one is screwed anyway.
Not if there's a workaround...
However, the erratum says "MMU page", not "4K region", so I suppose if
we have a pinned 8M page the problem could only occur at the end of the
8M (by which point the text segment should have ended).
The wording makes me wonder why not a dcbi would fix the problem too.
Invalidate the problem cache lines and let the branch resolve.
Where would you put the dcbi? How do you regain control after that
cache line has been refilled, but before code flows back to the bad branch?
-Scott
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
