[PATCH 15/30] x86, kaiser: map entry stack variables

From: Dave Hansen There are times where the kernel is entered but there is not a safe stack, like at SYSCALL entry. To obtain a safe stack, the per-cpu variables 'rsp_scratch' and 'cpu_current_top_of_stack' are used to save the old %rsp value and to find where the

[PATCH 15/30] x86, kaiser: map entry stack variables

From: Dave Hansen There are times where the kernel is entered but there is not a safe stack, like at SYSCALL entry. To obtain a safe stack, the per-cpu variables 'rsp_scratch' and 'cpu_current_top_of_stack' are used to save the old %rsp value and to find where the kernel stack should start.

[PATCH 15/30] x86, kaiser: map entry stack variables

From: Dave Hansen There are times that we enter the kernel and do not have a safe stack, like at SYSCALL entry. We use the per-cpu vairables 'rsp_scratch' and 'cpu_current_top_of_stack' to save off the old %rsp and find a safe place to have a stack. You can not

[PATCH 15/30] x86, kaiser: map entry stack variables

From: Dave Hansen There are times that we enter the kernel and do not have a safe stack, like at SYSCALL entry. We use the per-cpu vairables 'rsp_scratch' and 'cpu_current_top_of_stack' to save off the old %rsp and find a safe place to have a stack. You can not directly manipulate the CR3