diff options
| author | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2005-06-28 17:42:53 +0000 |
|---|---|---|
| committer | kaf24@firebug.cl.cam.ac.uk <kaf24@firebug.cl.cam.ac.uk> | 2005-06-28 17:42:53 +0000 |
| commit | 793aa523b8b977e3161ac953d36c0d8d632a2e2e (patch) | |
| tree | 1ae9beac7ee4e0a89f05b7fc885f978e2198491f | |
| parent | a575a4a3a8917a7249751537752831cc53cf573f (diff) | |
| download | xen-793aa523b8b977e3161ac953d36c0d8d632a2e2e.tar.gz xen-793aa523b8b977e3161ac953d36c0d8d632a2e2e.tar.bz2 xen-793aa523b8b977e3161ac953d36c0d8d632a2e2e.zip | |
bitkeeper revision 1.1767 (42c18c1dNRHfk7ZFajLHHtesQcrKlg)
At the time of debugging the fs segment problem, I noticed this bug (and
was able to test it).
Signed-off-by: Jun Nakajima <jun.nakajima@intel.com>
| -rw-r--r-- | linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S b/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S index 0285860d73..efc178ae47 100644 --- a/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S +++ b/linux-2.6.11-xen-sparse/arch/xen/x86_64/kernel/entry.S @@ -769,11 +769,11 @@ ENTRY(failsafe_callback) .section .fixup,"ax"; \ 6: movq $0,(%rsp); \ jmp 1b; \ -7: movq $0,(%rsp); \ +7: movq $0,8(%rsp); \ jmp 2b; \ -8: movq $0,(%rsp); \ +8: movq $0,16(%rsp); \ jmp 3b; \ -9: movq $0,(%rsp); \ +9: movq $0,24(%rsp); \ jmp 4b; \ .previous; \ .section __ex_table,"a";\ |