linux-kernel - [RFC][patch 0/5] clocksource cleanup / improvement

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-next>] [day] [month] [year] [list]

Message-Id: <20090721191745.788551122@de.ibm.com>
Date:	Tue, 21 Jul 2009 21:17:45 +0200
From:	Martin Schwidefsky <schwidefsky@...ibm.com>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>,
	john stultz <johnstul@...ibm.com>
Subject: [RFC][patch 0/5] clocksource cleanup / improvement

Greetings,
I had a go at the clocksource code and tried to make it better. The
first 4 patches contain some code cleanup and improve the separation
between timekeeping.c and clocksource.[ch].
Patch #5 is the one with the real change: the switch to a new clock
source is now done with stop_machine instead of checking with every
wall time update. A clocksource change is an extremely rare thing,
to use stop_machine seems reasonable to me.

What I'd like to do is to make the content of struct clocksource
private to clocksource.c and clocksource.h. The biggest road-block
to get there is update_wall_time. I stared at it for hours and then
gave up. A bit of unfinished business ..

The clocksource patches have been created against todays upstream
tree plus the patches from the tip tree, if anyone wants to try them
you need to pull from:
    git://git.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip

-- 
blue skies,
   Martin.

"Reality continues to ruin my life." - Calvin.

--
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/