On Sat, Feb 1, 2014 at 7:32 AM, wrote:
> From: Stefani Seibold
>
> This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
> into an additonal file vsyscall_gtod.c to make the functionality
> available for x86 32 bit kernel.
>
> It also adds a new vsyscall_32.c which setup the VVAR
From: Stefani Seibold
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani Seibold
---
Am Donnerstag, den 30.01.2014, 16:10 -0800 schrieb Andi Kleen:
> > @@ -1335,7 +1335,6 @@ config ARCH_SPARSEMEM_ENABLE
> >
> > config ARCH_SPARSEMEM_DEFAULT
> > def_bool y
> > - depends on X86_64
>
> Is that really needed? Why does the vdso need sparsemem?
>
No, it is from the previous
Am Donnerstag, den 30.01.2014, 16:10 -0800 schrieb Andi Kleen:
@@ -1335,7 +1335,6 @@ config ARCH_SPARSEMEM_ENABLE
config ARCH_SPARSEMEM_DEFAULT
def_bool y
- depends on X86_64
Is that really needed? Why does the vdso need sparsemem?
No, it is from the previous patch. I will
From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani
On Sat, Feb 1, 2014 at 7:32 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new
> @@ -1335,7 +1335,6 @@ config ARCH_SPARSEMEM_ENABLE
>
> config ARCH_SPARSEMEM_DEFAULT
> def_bool y
> - depends on X86_64
Is that really needed? Why does the vdso need sparsemem?
>
> static inline void __user *arch_compat_alloc_user_space(long len)
> {
> +#ifdef CONFIG_X86_32
>
Am Donnerstag, den 30.01.2014, 11:51 -0800 schrieb Andy Lutomirski:
> On Thu, Jan 30, 2014 at 11:27 AM, Stefani Seibold wrote:
> > Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
> >> On Thu, Jan 30, 2014 at 2:49 AM, wrote:
> >> > diff --git a/arch/x86/include/asm/compat.h
On Thu, Jan 30, 2014 at 11:27 AM, Stefani Seibold wrote:
> Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
>> On Thu, Jan 30, 2014 at 2:49 AM, wrote:
>> > diff --git a/arch/x86/include/asm/compat.h b/arch/x86/include/asm/compat.h
>> > index 59c6c40..45ba688 100644
>> > ---
Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
> On Thu, Jan 30, 2014 at 2:49 AM, wrote:
> > diff --git a/arch/x86/include/asm/compat.h b/arch/x86/include/asm/compat.h
> > index 59c6c40..45ba688 100644
> > --- a/arch/x86/include/asm/compat.h
> > +++
On Thu, Jan 30, 2014 at 2:49 AM, wrote:
> From: Stefani Seibold
>
> This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
> into an additonal file vsyscall_gtod.c to make the functionality
> available for x86 32 bit kernel.
>
> It also adds a new vsyscall_32.c which setup the
From: Stefani Seibold
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani Seibold
---
From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new vsyscall_32.c which setup the VVAR page.
Signed-off-by: Stefani
On Thu, Jan 30, 2014 at 2:49 AM, stef...@seibold.net wrote:
From: Stefani Seibold stef...@seibold.net
This patch move the vsyscall_gtod_data handling out of vsyscall_64.c
into an additonal file vsyscall_gtod.c to make the functionality
available for x86 32 bit kernel.
It also adds a new
Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
On Thu, Jan 30, 2014 at 2:49 AM, stef...@seibold.net wrote:
diff --git a/arch/x86/include/asm/compat.h b/arch/x86/include/asm/compat.h
index 59c6c40..45ba688 100644
--- a/arch/x86/include/asm/compat.h
+++
On Thu, Jan 30, 2014 at 11:27 AM, Stefani Seibold stef...@seibold.net wrote:
Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
On Thu, Jan 30, 2014 at 2:49 AM, stef...@seibold.net wrote:
diff --git a/arch/x86/include/asm/compat.h b/arch/x86/include/asm/compat.h
index
Am Donnerstag, den 30.01.2014, 11:51 -0800 schrieb Andy Lutomirski:
On Thu, Jan 30, 2014 at 11:27 AM, Stefani Seibold stef...@seibold.net wrote:
Am Donnerstag, den 30.01.2014, 10:05 -0800 schrieb Andy Lutomirski:
On Thu, Jan 30, 2014 at 2:49 AM, stef...@seibold.net wrote:
diff --git
@@ -1335,7 +1335,6 @@ config ARCH_SPARSEMEM_ENABLE
config ARCH_SPARSEMEM_DEFAULT
def_bool y
- depends on X86_64
Is that really needed? Why does the vdso need sparsemem?
static inline void __user *arch_compat_alloc_user_space(long len)
{
+#ifdef CONFIG_X86_32
+
18 matches
Mail list logo
