Message-ID: <4F4E859E.9030902@mit.edu>
Date: Wed, 29 Feb 2012 12:07:58 -0800
From: Andy Lutomirski <luto@MIT.EDU>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120216 Thunderbird/10.0.1
MIME-Version: 1.0
Newsgroups: gmane.linux.kernel
To: Thomas Gleixner <tglx@linutronix.de>
CC: LKML <linux-kernel@vger.kernel.org>, John Stultz <john.stultz@linaro.org>,
        Ingo Molnar <mingo@elte.hu>, Peter Anvin <hpa@zytor.com>,
        Peter Zijlstra <peterz@infradead.org>, Tony Luck <tony.luck@intel.com>
Subject: Re: [patch 0/4] time/timekeeping: Simplify vsyscall locking
References: <20120228194200.180923135@linutronix.de>
In-Reply-To: <20120228194200.180923135@linutronix.de>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 779
Lines: 21

On 02/28/2012 11:46 AM, Thomas Gleixner wrote:
> vsyscall updates have a separate seqlock which nests into
> xtime_lock. There is no point to grab another lock for nothing. All it
> needs is to update the seqcount which is user space visible.
> 
> The following series cleans that up.

FWIW, patches 2 and 3 are
Reviewed-by: Andy Lutomirski <luto@amacapital.net>

Can you let me know when these hit a git tree somewhere?  I have two
more vdso clock speedups I want to send for 3.4, and I'll rebase them on
top of these.

Thanks,
Andy
--
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/