From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933916AbXCPQdn (ORCPT ); Fri, 16 Mar 2007 12:33:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933937AbXCPQdn (ORCPT ); Fri, 16 Mar 2007 12:33:43 -0400 Received: from gw.goop.org ([64.81.55.164]:41668 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933916AbXCPQdm (ORCPT ); Fri, 16 Mar 2007 12:33:42 -0400 Message-ID: <45FAC6E6.5090000@goop.org> Date: Fri, 16 Mar 2007 09:33:42 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 1.5.0.10 (X11/20070302) MIME-Version: 1.0 To: Ingo Molnar CC: "Eric W. Biederman" , Zachary Amsden , Linux Kernel Mailing List , Jan Beulich , Rusty Russell , Andi Kleen , Chris Wright , Andrew Morton , Linus Torvalds , Virtualization Mailing List Subject: Re: [RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT References: <45FA054F.6020107@vmware.com> <45FAC4EF.4060305@goop.org> <20070316163118.GA12999@elte.hu> In-Reply-To: <20070316163118.GA12999@elte.hu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.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