> From: Dave Hansen <[email protected]>
>
> The "SYSENTER" stack is used for a lot more than SYSENTER now.
> Give it a better string to display in stack dumps.
>
> We should probably cleanse the 64-bit code of the remaining
> "SYSENTER" nomenclature too at some point.
>
> Signed-off-by: Dave Hansen <[email protected]>
> ---
>
> b/arch//x86/kernel/dumpstack_64.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff -puN arch//x86/kernel/dumpstack_64.c~SYSENTER-rename
> arch//x86/kernel/dumpstack_64.c
> --- a/arch//x86/kernel/dumpstack_64.c~SYSENTER-rename 2017-12-01
> 12:43:16.768707737 -0800
> +++ b/arch//x86/kernel/dumpstack_64.c 2017-12-01 13:19:21.741702337 -0800
> @@ -37,8 +37,14 @@ const char *stack_type_name(enum stack_t
> if (type == STACK_TYPE_IRQ)
> return "IRQ";
>
> - if (type == STACK_TYPE_SYSENTER)
> - return "SYSENTER";
> + if (type == STACK_TYPE_SYSENTER) {
> + /*
> + * On 64-bit, we have a generic entry stack that we
> + * use for all the kernel try points, including
> + * SYSENTER.
ITYM "kernel entry points".
- Kevin
