Re: [patch 0/4] time/timekeeping: Simplify vsyscall locking

[Andy Lutomirski]

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@xxxxxxxxxxxxxx>

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/