Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 19 Oct 2002 21:45:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 19 Oct 2002 21:45:05 -0400 Received: from 2-136.ctame701-1.telepar.net.br ([200.193.160.136]:37847 "EHLO 2-136.ctame701-1.telepar.net.br") by vger.kernel.org with ESMTP id ; Sat, 19 Oct 2002 21:45:04 -0400 Date: Sat, 19 Oct 2002 23:50:37 -0200 (BRST) From: Rik van Riel X-X-Sender: riel@imladris.surriel.com To: Jeff Dike cc: Andi Kleen , john stultz , Linus Torvalds , andrea , lkml , george anzinger , Stephen Hemminger Subject: Re: [PATCH] linux-2.5.43_vsyscall_A0 In-Reply-To: <200210190450.XAA06161@ccure.karaya.com> Message-ID: X-spambait: aardvark@kernelnewbies.org X-spammeplease: aardvark@nl.linux.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 955 Lines: 23 On Fri, 18 Oct 2002, Jeff Dike wrote: > My preferred solution would be for libc to ask the kernel where the > vsyscall area is. That's reasonably clean and virtualizable. Andrea > doesn't like it because it adds a few instructions to the vsyscall > address calculation. Sounds like the best solution indeed, especially when keeping in mind the strange people who want to run with a different user:kernel split or statically linked binaries at fun addresses so they've got more space for their fortran arrays ;) Rik -- Bravely reimplemented by the knights who say "NIH". http://www.surriel.com/ http://distro.conectiva.com/ Current spamtrap: october@surriel.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/