2005-04-16 16:20:36 -06:00
|
|
|
/* Copyright 2004,2005 Pavel Machek <pavel@suse.cz>, Andi Kleen <ak@suse.de>, Rafael J. Wysocki <rjw@sisk.pl>
|
|
|
|
|
*
|
|
|
|
|
* Distribute under GPLv2.
|
|
|
|
|
*
|
|
|
|
|
* swsusp_arch_resume may not use any stack, nor any variable that is
|
|
|
|
|
* not "NoSave" during copying pages:
|
|
|
|
|
*
|
|
|
|
|
* Its rewriting one kernel image with another. What is stack in "old"
|
|
|
|
|
* image could very well be data page in "new" image, and overwriting
|
|
|
|
|
* your own stack under you is bad idea.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
.text
|
|
|
|
|
#include <linux/linkage.h>
|
|
|
|
|
#include <asm/segment.h>
|
|
|
|
|
#include <asm/page.h>
|
2005-09-09 13:28:48 -06:00
|
|
|
#include <asm/asm-offsets.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
ENTRY(swsusp_arch_suspend)
|
|
|
|
|
|
|
|
|
|
movq %rsp, saved_context_esp(%rip)
|
|
|
|
|
movq %rax, saved_context_eax(%rip)
|
|
|
|
|
movq %rbx, saved_context_ebx(%rip)
|
|
|
|
|
movq %rcx, saved_context_ecx(%rip)
|
|
|
|
|
movq %rdx, saved_context_edx(%rip)
|
|
|
|
|
movq %rbp, saved_context_ebp(%rip)
|
|
|
|
|
movq %rsi, saved_context_esi(%rip)
|
|
|
|
|
movq %rdi, saved_context_edi(%rip)
|
|
|
|
|
movq %r8, saved_context_r08(%rip)
|
|
|
|
|
movq %r9, saved_context_r09(%rip)
|
|
|
|
|
movq %r10, saved_context_r10(%rip)
|
|
|
|
|
movq %r11, saved_context_r11(%rip)
|
|
|
|
|
movq %r12, saved_context_r12(%rip)
|
|
|
|
|
movq %r13, saved_context_r13(%rip)
|
|
|
|
|
movq %r14, saved_context_r14(%rip)
|
|
|
|
|
movq %r15, saved_context_r15(%rip)
|
|
|
|
|
pushfq ; popq saved_context_eflags(%rip)
|
|
|
|
|
|
|
|
|
|
call swsusp_save
|
|
|
|
|
ret
|
|
|
|
|
|
[PATCH] x86_64: Set up safe page tables during resume
The following patch makes swsusp avoid the possible temporary corruption
of page translation tables during resume on x86-64. This is achieved by
creating a copy of the relevant page tables that will not be modified by
swsusp and can be safely used by it on resume.
The problem is that during resume on x86-64 swsusp may temporarily
corrupt the page tables used for the direct mapping of RAM. If that
happens, a page fault occurs and cannot be handled properly, which leads
to the solid hang of the affected system. This leads to the loss of the
system's state from before suspend and may result in the loss of data or
the corruption of filesystems, so it is a serious issue. Also, it
appears to happen quite often (for me, as often as 50% of the time).
The problem is related to the fact that (at least) one of the PMD
entries used in the direct memory mapping (starting at PAGE_OFFSET)
points to a page table the physical address of which is much greater
than the physical address of the PMD entry itself. Moreover,
unfortunately, the physical address of the page table before suspend
(i.e. the one stored in the suspend image) happens to be different to
the physical address of the corresponding page table used during resume
(i.e. the one that is valid right before swsusp_arch_resume() in
arch/x86_64/kernel/suspend_asm.S is executed). Thus while the image is
restored, the "offending" PMD entry gets overwritten, so it does not
point to the right physical address any more (i.e. there's no page
table at the address pointed to by it, because it points to the address
the page table has been at during suspend). Consequently, if the PMD
entry is used later on, and it _is_ used in the process of copying the
image pages, a page fault occurs, but it cannot be handled in the normal
way and the system hangs.
In principle we can call create_resume_mapping() from
swsusp_arch_resume() (ie. from suspend_asm.S), but then the memory
allocations in create_resume_mapping(), resume_pud_mapping(), and
resume_pmd_mapping() must be made carefully so that we use _only_
NosaveFree pages in them (the other pages are overwritten by the loop in
swsusp_arch_resume()). Additionally, we are in atomic context at that
time, so we cannot use GFP_KERNEL. Moreover, if one of the allocations
fails, we should free all of the allocated pages, so we need to trace
them somehow.
All of this is done in the appended patch, except that the functions
populating the page tables are located in arch/x86_64/kernel/suspend.c
rather than in init.c. It may be done in a more elegan way in the
future, with the help of some swsusp patches that are in the works now.
[AK: move some externs into headers, renamed a function]
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-09 13:19:40 -06:00
|
|
|
ENTRY(restore_image)
|
|
|
|
|
/* switch to temporary page tables */
|
|
|
|
|
movq $__PAGE_OFFSET, %rdx
|
|
|
|
|
movq temp_level4_pgt(%rip), %rax
|
|
|
|
|
subq %rdx, %rax
|
|
|
|
|
movq %rax, %cr3
|
|
|
|
|
/* Flush TLB */
|
2005-04-16 16:20:36 -06:00
|
|
|
movq mmu_cr4_features(%rip), %rax
|
|
|
|
|
movq %rax, %rdx
|
|
|
|
|
andq $~(1<<7), %rdx # PGE
|
|
|
|
|
movq %rdx, %cr4; # turn off PGE
|
|
|
|
|
movq %cr3, %rcx; # flush TLB
|
|
|
|
|
movq %rcx, %cr3;
|
|
|
|
|
movq %rax, %cr4; # turn PGE back on
|
|
|
|
|
|
2006-09-26 00:32:52 -06:00
|
|
|
movq restore_pblist(%rip), %rdx
|
2005-04-16 16:20:36 -06:00
|
|
|
loop:
|
|
|
|
|
testq %rdx, %rdx
|
|
|
|
|
jz done
|
|
|
|
|
|
|
|
|
|
/* get addresses from the pbe and copy the page */
|
|
|
|
|
movq pbe_address(%rdx), %rsi
|
|
|
|
|
movq pbe_orig_address(%rdx), %rdi
|
|
|
|
|
movq $512, %rcx
|
|
|
|
|
rep
|
|
|
|
|
movsq
|
|
|
|
|
|
|
|
|
|
/* progress to the next pbe */
|
|
|
|
|
movq pbe_next(%rdx), %rdx
|
|
|
|
|
jmp loop
|
|
|
|
|
done:
|
[PATCH] x86_64: Set up safe page tables during resume
The following patch makes swsusp avoid the possible temporary corruption
of page translation tables during resume on x86-64. This is achieved by
creating a copy of the relevant page tables that will not be modified by
swsusp and can be safely used by it on resume.
The problem is that during resume on x86-64 swsusp may temporarily
corrupt the page tables used for the direct mapping of RAM. If that
happens, a page fault occurs and cannot be handled properly, which leads
to the solid hang of the affected system. This leads to the loss of the
system's state from before suspend and may result in the loss of data or
the corruption of filesystems, so it is a serious issue. Also, it
appears to happen quite often (for me, as often as 50% of the time).
The problem is related to the fact that (at least) one of the PMD
entries used in the direct memory mapping (starting at PAGE_OFFSET)
points to a page table the physical address of which is much greater
than the physical address of the PMD entry itself. Moreover,
unfortunately, the physical address of the page table before suspend
(i.e. the one stored in the suspend image) happens to be different to
the physical address of the corresponding page table used during resume
(i.e. the one that is valid right before swsusp_arch_resume() in
arch/x86_64/kernel/suspend_asm.S is executed). Thus while the image is
restored, the "offending" PMD entry gets overwritten, so it does not
point to the right physical address any more (i.e. there's no page
table at the address pointed to by it, because it points to the address
the page table has been at during suspend). Consequently, if the PMD
entry is used later on, and it _is_ used in the process of copying the
image pages, a page fault occurs, but it cannot be handled in the normal
way and the system hangs.
In principle we can call create_resume_mapping() from
swsusp_arch_resume() (ie. from suspend_asm.S), but then the memory
allocations in create_resume_mapping(), resume_pud_mapping(), and
resume_pmd_mapping() must be made carefully so that we use _only_
NosaveFree pages in them (the other pages are overwritten by the loop in
swsusp_arch_resume()). Additionally, we are in atomic context at that
time, so we cannot use GFP_KERNEL. Moreover, if one of the allocations
fails, we should free all of the allocated pages, so we need to trace
them somehow.
All of this is done in the appended patch, except that the functions
populating the page tables are located in arch/x86_64/kernel/suspend.c
rather than in init.c. It may be done in a more elegan way in the
future, with the help of some swsusp patches that are in the works now.
[AK: move some externs into headers, renamed a function]
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Signed-off-by: Andi Kleen <ak@suse.de>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-10-09 13:19:40 -06:00
|
|
|
/* go back to the original page tables */
|
|
|
|
|
leaq init_level4_pgt(%rip), %rax
|
|
|
|
|
subq $__START_KERNEL_map, %rax
|
|
|
|
|
movq %rax, %cr3
|
2005-04-16 16:20:36 -06:00
|
|
|
/* Flush TLB, including "global" things (vmalloc) */
|
|
|
|
|
movq mmu_cr4_features(%rip), %rax
|
|
|
|
|
movq %rax, %rdx
|
|
|
|
|
andq $~(1<<7), %rdx; # PGE
|
|
|
|
|
movq %rdx, %cr4; # turn off PGE
|
|
|
|
|
movq %cr3, %rcx; # flush TLB
|
|
|
|
|
movq %rcx, %cr3
|
|
|
|
|
movq %rax, %cr4; # turn PGE back on
|
|
|
|
|
|
|
|
|
|
movl $24, %eax
|
|
|
|
|
movl %eax, %ds
|
|
|
|
|
|
|
|
|
|
movq saved_context_esp(%rip), %rsp
|
|
|
|
|
movq saved_context_ebp(%rip), %rbp
|
|
|
|
|
/* Don't restore %rax, it must be 0 anyway */
|
|
|
|
|
movq saved_context_ebx(%rip), %rbx
|
|
|
|
|
movq saved_context_ecx(%rip), %rcx
|
|
|
|
|
movq saved_context_edx(%rip), %rdx
|
|
|
|
|
movq saved_context_esi(%rip), %rsi
|
|
|
|
|
movq saved_context_edi(%rip), %rdi
|
|
|
|
|
movq saved_context_r08(%rip), %r8
|
|
|
|
|
movq saved_context_r09(%rip), %r9
|
|
|
|
|
movq saved_context_r10(%rip), %r10
|
|
|
|
|
movq saved_context_r11(%rip), %r11
|
|
|
|
|
movq saved_context_r12(%rip), %r12
|
|
|
|
|
movq saved_context_r13(%rip), %r13
|
|
|
|
|
movq saved_context_r14(%rip), %r14
|
|
|
|
|
movq saved_context_r15(%rip), %r15
|
|
|
|
|
pushq saved_context_eflags(%rip) ; popfq
|
|
|
|
|
|
|
|
|
|
xorq %rax, %rax
|
|
|
|
|
|
|
|
|
|
ret
|
