From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT Date: Fri, 16 Mar 2007 09:33:42 -0700 Message-ID: <45FAC6E6.5090000@goop.org> References: <45FA054F.6020107@vmware.com> <45FAC4EF.4060305@goop.org> <20070316163118.GA12999@elte.hu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20070316163118.GA12999@elte.hu> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.osdl.org Errors-To: virtualization-bounces@lists.osdl.org To: Ingo Molnar Cc: Chris Wright , Linus Torvalds , "Eric W. Biederman" , Andrew Morton , Virtualization Mailing List , Jan Beulich , Linux Kernel Mailing List List-Id: virtualization@lists.linuxfoundation.org Ingo Molnar wrote: > that's what is the case right now, but much of the intention behind the = > vma based vDSO is to enable per-process randomized vdso locations, and = > various distributions do that. So the 'modern' vDSO concept is very much = > relocatable. No, the point is that it never needs relocating. The kernel can map it anywhere and userspace can cope. Its only the broken glibcs which require relocation. J