summaryrefslogtreecommitdiff
path: root/board/amcc/katmai/init.S
diff options
context:
space:
mode:
authorGrzegorz Bernacki <gjb@semihalf.com>2007-09-07 17:46:18 +0200
committerRafal Jaworowski <raj@semihalf.com>2007-09-07 17:46:18 +0200
commit15ee4734e4e08003d73d9ead3ca80e2a0672e427 (patch)
tree3f175cf322df88a775a2ce86cce0dfe8486abfc1 /board/amcc/katmai/init.S
parenta89cbbd27a60e6740772000fd0688ffba1c2576a (diff)
downloadu-boot-imx-15ee4734e4e08003d73d9ead3ca80e2a0672e427.zip
u-boot-imx-15ee4734e4e08003d73d9ead3ca80e2a0672e427.tar.gz
u-boot-imx-15ee4734e4e08003d73d9ead3ca80e2a0672e427.tar.bz2
[PPC440SPe] Convert machine check exceptions handling
Convert using fixup mechanism to suppressing MCK for the duration of config read/write transaction: while fixups work fine with the case of a precise exception, we identified a major drawback with this approach when there's an imprecise case. In this scenario there is the following race condition: the fixup is (by design) set to catch the instruction following the one actually causing the exception; if an interrupt (e.g. decrementer) happens between those two instructions, the ISR code is executed before the fixup handler the machine check is no longer protected by the fixup handler as it appears as within the ISR code. In consequence the fixup approach is being phased out and replaced with explicit suppressing of MCK during a PCIe config read/write cycle. Signed-off-by: Grzegorz Bernacki <gjb@semihalf.com>
Diffstat (limited to 'board/amcc/katmai/init.S')
0 files changed, 0 insertions, 0 deletions