Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757994AbZGQWzd (ORCPT ); Fri, 17 Jul 2009 18:55:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757972AbZGQWzc (ORCPT ); Fri, 17 Jul 2009 18:55:32 -0400 Received: from e6.ny.us.ibm.com ([32.97.182.146]:57064 "EHLO e6.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757945AbZGQWzc (ORCPT ); Fri, 17 Jul 2009 18:55:32 -0400 Subject: Re: Duplicate vsyscall/vdso gettimeofday implementations on x86_64 From: john stultz To: Andi Kleen Cc: Ingo Molnar , Thomas Gleixner , lkml In-Reply-To: <87eisfvtzv.fsf@basil.nowhere.org> References: <1247868130.8334.40.camel@localhost.localdomain> <87eisfvtzv.fsf@basil.nowhere.org> Content-Type: text/plain Date: Fri, 17 Jul 2009 15:54:44 -0700 Message-Id: <1247871284.8334.42.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.24.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 707 Lines: 22 On Sat, 2009-07-18 at 00:12 +0200, Andi Kleen wrote: > john stultz writes: > > > I think the implementation in vclock_gettime.c is nice, as it mostly > > reuses the clock_gettime() code, but I don't think it actually gets > > called. > > It depends on what glibc uses. Hrmm. Can we deprecate the old method and push glibc to use the new one? If we remove it the vsyscall interface will old glibc's fall-back gracefully? thanks -john -- 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/