linux-kernel - Re: [patch 00/15] clocksource / timekeeping rework V4 (resend V3 + bug fix)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0908141608120.1283@localhost.localdomain>
Date:	Fri, 14 Aug 2009 16:08:57 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Martin Schwidefsky <schwidefsky@...ibm.com>
cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	john stultz <johnstul@...ibm.com>
Subject: Re: [patch 00/15] clocksource / timekeeping rework V4 (resend V3 +
 bug fix)

Martin,

On Fri, 14 Aug 2009, Martin Schwidefsky wrote:

> Greetings,
> version 4 of the clocksource / timekeeping cleanup patches. If you
> wonder why version 3 did not show up on the mailing list: I had a
> hiccup with quilt which did strange things to the message ids and
> the post to lkml got rejected. Sorry for the spamming of the people
> on Cc.
> 
> John pointed out a subtle bug in v3 of the patch set with the reset of
> the cycle_last value in timekeeping_resume. Fixed in v4.
> 
> The latest additions are:
> 1) Change read_persistent_clock to return a struct timespec instead of
>    an unsigned long with the number of seconds.
> 2) Introduce read_boot_clock to initialize wall_to_monotonic.
> 3) Move the reset of cycle_last to zero from the timekeeping code to
>    the TSC code.
> 
> The patch set is based on todays upstream tree plus the patches from
> the tip tree, if anyone wants to try them you need to pull from the
> master branch of
>     git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip
> 
> Keeping the fingers crossed that this is now really done.
> John already gave his thumbs up for the patch series, so the next
> logical question is who is going to sit on the patches until the merge
> window is opened? I can certainly create a git branch on git390 for
> them, but the patches depend on some patches in the x86-tip tree.
> Thomas, any thoughts?

I'm going through them and pick them up into -tip.

Thanks,

	tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/