Re: [PATCH PTI] Fixup "x86/entry/64: Use a per-CPU trampoline stack for IDT entries"

2017-12-06 Thread Juergen Gross
On 06/12/17 07:00, Andy Lutomirski wrote: > Add to commit message: > > Using a trampoline stack would obnoxious for Xen PV because Xen PV > enters entry_SYSCALL_64_after_hwframe on the stack indicated by sp0. > This could be fixed, but I think it's nice to ensure the entry code > can still work

Re: [PATCH PTI] Fixup "x86/entry/64: Use a per-CPU trampoline stack for IDT entries"

2017-12-06 Thread Juergen Gross
On 06/12/17 07:00, Andy Lutomirski wrote: > Add to commit message: > > Using a trampoline stack would obnoxious for Xen PV because Xen PV > enters entry_SYSCALL_64_after_hwframe on the stack indicated by sp0. > This could be fixed, but I think it's nice to ensure the entry code > can still work

[PATCH PTI] Fixup "x86/entry/64: Use a per-CPU trampoline stack for IDT entries"

2017-12-05 Thread Andy Lutomirski
Add to commit message: Using a trampoline stack would obnoxious for Xen PV because Xen PV enters entry_SYSCALL_64_after_hwframe on the stack indicated by sp0. This could be fixed, but I think it's nice to ensure the entry code can still work without a trampoline stack. So this patch doesn't use

[PATCH PTI] Fixup "x86/entry/64: Use a per-CPU trampoline stack for IDT entries"

2017-12-05 Thread Andy Lutomirski
Add to commit message: Using a trampoline stack would obnoxious for Xen PV because Xen PV enters entry_SYSCALL_64_after_hwframe on the stack indicated by sp0. This could be fixed, but I think it's nice to ensure the entry code can still work without a trampoline stack. So this patch doesn't use