From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752316Ab1E2JvX (ORCPT ); Sun, 29 May 2011 05:51:23 -0400 Received: from mail-vx0-f174.google.com ([209.85.220.174]:37830 "EHLO mail-vx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750915Ab1E2JvV convert rfc822-to-8bit (ORCPT ); Sun, 29 May 2011 05:51:21 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=fEV3PLZ5ERh3ZQ2yt8o5AnSpTwmdMpyz2SG6AcorjG4jSfDvca8tBAqdKp3ozQKegB F2hIvt8EU/VpHsvliLcjXEP0A3nZl0h5lb8CxA0mwIAguOuteNdD6NZLwkSbJ75WI52M OgWxVNjNFzi2+KCjsVtfDl8d6SswdCTauCiE0= MIME-Version: 1.0 In-Reply-To: References: <4DDEC589.3010201@mit.edu> <20110527061208.GB9260@elte.hu> Date: Sun, 29 May 2011 11:51:20 +0200 Message-ID: Subject: Re: [GIT pull] x86 vdso updates From: richard -rw- weinberger To: Andrew Lutomirski Cc: Ingo Molnar , Thomas Gleixner , Linus Torvalds , Andrew Morton , x86@kernel.org, LKML Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 27, 2011 at 5:05 PM, Andrew Lutomirski wrote: > On Fri, May 27, 2011 at 10:59 AM, richard -rw- weinberger > wrote: >> On Fri, May 27, 2011 at 2:10 PM, Andrew Lutomirski wrote: >>> On Fri, May 27, 2011 at 7:59 AM, richard -rw- weinberger >>> If this is considered enough of a regression, then I guess we can >>> leave vsyscall64 around for awhile, but it will require extra work in >>> the soon-to-be syscall emulation hack to make sure that UML can still >>> trap the syscall. >> >> As long the time within UML is synchronous with the host everything is >> fine, right? > > I think so.  I haven't used UML in a long time. > >> So, as _last_ choice we could disable the ability to change the time within UML. >> >> IMHO it's not a big deal when getcpu() returns a wrong CPU layout on UML. >> >>> The real solution is to fix glibc to use the vDSO which should avoid >>> this problem entirely. >> Yesterday I had a closer look at 64bit UML. Glibc is always using vsyscalls because 64bit UML does not support the vDSO. On 32bit UML simply scans the ELF auxiliary vector provided by the host to get the address of the vDSO. How can I get this address on a 64bit host? -- Thanks, //richard