diff options
| author | Michael Neuling <michael.neuling@au1.ibm.com> | 2013-04-24 00:30:09 +0000 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2013-05-07 19:57:20 -0700 |
| commit | 74f31cf3c186bc0189ad560fadfc03dd9aa2f806 (patch) | |
| tree | a80837e73826ab7ec51d2ef6b90b9fd3eaad2449 /arch/powerpc | |
| parent | 27a2f7c50c87691fa4b6a0a8a77f779b8bbe648c (diff) | |
| download | kernel_samsung_aries-74f31cf3c186bc0189ad560fadfc03dd9aa2f806.zip kernel_samsung_aries-74f31cf3c186bc0189ad560fadfc03dd9aa2f806.tar.gz kernel_samsung_aries-74f31cf3c186bc0189ad560fadfc03dd9aa2f806.tar.bz2 | |
powerpc: Add isync to copy_and_flush
commit 29ce3c5073057991217916abc25628e906911757 upstream.
In __after_prom_start we copy the kernel down to zero in two calls to
copy_and_flush. After the first call (copy from 0 to copy_to_here:)
we jump to the newly copied code soon after.
Unfortunately there's no isync between the copy of this code and the
jump to it. Hence it's possible that stale instructions could still be
in the icache or pipeline before we branch to it.
We've seen this on real machines and it's results in no console output
after:
calling quiesce...
returning from prom_init
The below adds an isync to ensure that the copy and flushing has
completed before any branching to the new instructions occurs.
Signed-off-by: Michael Neuling <mikey@neuling.org>
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'arch/powerpc')
| -rw-r--r-- | arch/powerpc/kernel/head_64.S | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S index e8befef..a5031c3 100644 --- a/arch/powerpc/kernel/head_64.S +++ b/arch/powerpc/kernel/head_64.S @@ -492,6 +492,7 @@ _GLOBAL(copy_and_flush) sync addi r5,r5,8 addi r6,r6,8 + isync blr .align 8 |