[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140131001034.GB2350@tassilo.jf.intel.com>
Date: Thu, 30 Jan 2014 16:10:34 -0800
From: Andi Kleen <ak@...ux.intel.com>
To: stefani@...bold.net
Cc: gregkh@...uxfoundation.org, linux-kernel@...r.kernel.org,
x86@...nel.org, tglx@...utronix.de, mingo@...hat.com,
hpa@...or.com, aarcange@...hat.com, john.stultz@...aro.org,
luto@...capital.net, xemul@...allels.com, gorcunov@...nvz.org,
andriy.shevchenko@...ux.intel.com, Martin.Runge@...de-schwarz.com,
Andreas.Brief@...de-schwarz.com
Subject: Re: [PATCH 1/4] Make vsyscall_gtod_data handling x86 generic
> @@ -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
> + struct pt_regs *regs = task_pt_regs(current);
> + return (void __user *)regs->sp - len;
> +#else
> compat_uptr_t sp;
and that? why does a vdso need to allocate things on the user page?
-Andi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists