Re: [PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-26 Thread Ingo Molnar
* Thomas Gleixner wrote: > On Fri, 24 Nov 2017, Ingo Molnar wrote: > > +void kaiser_add_mapping_cpu_entry(int cpu) > > +{ > > + kaiser_add_user_map_early(get_cpu_gdt_ro(cpu), PAGE_SIZE, > > + __PAGE_KERNEL_RO); > > + > > + /* includes the

Re: [PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-26 Thread Ingo Molnar
* Thomas Gleixner wrote: > On Fri, 24 Nov 2017, Ingo Molnar wrote: > > +void kaiser_add_mapping_cpu_entry(int cpu) > > +{ > > + kaiser_add_user_map_early(get_cpu_gdt_ro(cpu), PAGE_SIZE, > > + __PAGE_KERNEL_RO); > > + > > + /* includes the entry stack */ > > +

Re: [PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-25 Thread Thomas Gleixner
On Fri, 24 Nov 2017, Ingo Molnar wrote: > +void kaiser_add_mapping_cpu_entry(int cpu) > +{ > + kaiser_add_user_map_early(get_cpu_gdt_ro(cpu), PAGE_SIZE, > + __PAGE_KERNEL_RO); > + > + /* includes the entry stack */ > +

Re: [PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-25 Thread Thomas Gleixner
On Fri, 24 Nov 2017, Ingo Molnar wrote: > +void kaiser_add_mapping_cpu_entry(int cpu) > +{ > + kaiser_add_user_map_early(get_cpu_gdt_ro(cpu), PAGE_SIZE, > + __PAGE_KERNEL_RO); > + > + /* includes the entry stack */ > +

[PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-24 Thread Ingo Molnar
From: Dave Hansen There is now a special 'struct cpu_entry' area that contains all of the data needed to enter the kernel. It's mapped in the fixmap area and contains: * The GDT (hardware segment descriptor) * The TSS (thread information structure that points the

[PATCH 28/43] x86/mm/kaiser: Map cpu entry area

2017-11-24 Thread Ingo Molnar
From: Dave Hansen There is now a special 'struct cpu_entry' area that contains all of the data needed to enter the kernel. It's mapped in the fixmap area and contains: * The GDT (hardware segment descriptor) * The TSS (thread information structure that points the hardware to the various

Re: [PATCH 28/43] x86/mm/kaiser: Map CPU entry area

2017-11-24 Thread Peter Zijlstra
On Fri, Nov 24, 2017 at 10:14:33AM +0100, Ingo Molnar wrote: > + /* CPU 0's mapping is done in kaiser_init() */ > + if (cpu) > + kaiser_add_mapping_cpu_entry(cpu); This hard assumes CPU0 is the boot CPU. I know we dropped Voyager support a while back, but can/should we hard

Re: [PATCH 28/43] x86/mm/kaiser: Map CPU entry area

2017-11-24 Thread Peter Zijlstra
On Fri, Nov 24, 2017 at 10:14:33AM +0100, Ingo Molnar wrote: > + /* CPU 0's mapping is done in kaiser_init() */ > + if (cpu) > + kaiser_add_mapping_cpu_entry(cpu); This hard assumes CPU0 is the boot CPU. I know we dropped Voyager support a while back, but can/should we hard

[PATCH 28/43] x86/mm/kaiser: Map CPU entry area

2017-11-24 Thread Ingo Molnar
From: Dave Hansen There is now a special 'struct cpu_entry' area that contains all of the data needed to enter the kernel. It's mapped in the fixmap area and contains: * The GDT (hardware segment descriptor) * The TSS (thread information structure that points the

[PATCH 28/43] x86/mm/kaiser: Map CPU entry area

2017-11-24 Thread Ingo Molnar
From: Dave Hansen There is now a special 'struct cpu_entry' area that contains all of the data needed to enter the kernel. It's mapped in the fixmap area and contains: * The GDT (hardware segment descriptor) * The TSS (thread information structure that points the hardware to the various