From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1767259AbXCINLZ (ORCPT ); Fri, 9 Mar 2007 08:11:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1767271AbXCINLZ (ORCPT ); Fri, 9 Mar 2007 08:11:25 -0500 Received: from www.osadl.org ([213.239.205.134]:40205 "EHLO mail.tglx.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1767259AbXCINLY (ORCPT ); Fri, 9 Mar 2007 08:11:24 -0500 Subject: Re: [rfc][patch] futex: restartable futex_wait? From: Thomas Gleixner To: Nick Piggin Cc: Ingo Molnar , Linux Kernel Mailing List In-Reply-To: <20070309122417.GA15325@wotan.suse.de> References: <20070307153349.GA32404@wotan.suse.de> <20070308172902.GA16834@elte.hu> <20070309051038.GA12479@wotan.suse.de> <1173433115.3999.2.camel@chaos> <20070309122417.GA15325@wotan.suse.de> Content-Type: text/plain Date: Fri, 09 Mar 2007 14:10:53 +0100 Message-Id: <1173445853.3999.6.camel@chaos> Mime-Version: 1.0 X-Mailer: Evolution 2.8.3 (2.8.3-1.fc6) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2007-03-09 at 13:24 +0100, Nick Piggin wrote: > > > > 'time' here is relative, so the restarted syscall will do a /full/ wait > > > > again. > > > > > > But it has been modified by schedule_timeout? > > > > But this does not change the syscall registers, so it is restarted in > > the same way. We need a new futex OP for this, which takes absolute time > > like the PI futex op does. > > Forgive me if I'm missing something here, but I'm using the restart block > and saving the updated value of time in ->arg2, and using that as the new > time parameter passed into futex_wait from futex_wait_restart. Oops. I went into confusion mode. You are right, the restart block keeps that. tglx