Re: [Xen-devel] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size

On Wed, Feb 15, 2017 at 04:49:21PM +0100, Borislav Petkov wrote: > On Wed, Feb 15, 2017 at 07:40:51AM -0800, Thomas Garnier wrote: > > Why do you think they rely on it being static? The VSYSCALL address is > > not changed for example. > > I don't know, that's why I'm asking first. Userspace is

Re: [Xen-devel] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size

On Wed, Feb 15, 2017 at 07:40:51AM -0800, Thomas Garnier wrote: > Why do you think they rely on it being static? The VSYSCALL address is > not changed for example. I don't know, that's why I'm asking first. Userspace is known to pick different aspects of the kernel and deciding to use them for

Re: [Xen-devel] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size

On Wed, Feb 15, 2017 at 5:58 AM, Borislav Petkov wrote: > > On Tue, Feb 14, 2017 at 11:42:56AM -0800, Thomas Garnier wrote: > > This patch aligns MODULES_END to the beginning of the Fixmap section. > > It optimizes the space available for both sections. The address is > >

Re: [Xen-devel] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size

On Tue, Feb 14, 2017 at 11:42:56AM -0800, Thomas Garnier wrote: > This patch aligns MODULES_END to the beginning of the Fixmap section. > It optimizes the space available for both sections. The address is > pre-computed based on the number of pages required by the Fixmap > section. > > It will

[Xen-devel] [PATCH v3 1/4] x86/mm: Adapt MODULES_END based on Fixmap section size

This patch aligns MODULES_END to the beginning of the Fixmap section. It optimizes the space available for both sections. The address is pre-computed based on the number of pages required by the Fixmap section. It will allow GDT remapping in the Fixmap section. The current MODULES_END static