GENERIC_TIME patchset for x86_64
Get series with b4
b4 am 20061129025728.15379.50707.sendpatchset@localhostVersions newest first
- v1 Latest5 patches 5 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/5 | vsyscall-gtod support for GENERIC_TIMEinclude/ kernel/ | +9 | 0 replies | |
| 2/5 | hpet_address cleanuparch/ arch/ arch/ +1 more | +28 | 0 replies | |
| 3/5 | Split x86_64/kernel/time.c uparch/ arch/ arch/ +3 more | +658 | 0 replies | |
| 4/5 | Convert x86_64 to use GENERIC_TIMEarch/ arch/ arch/ +6 more | +133 | 5 replies | |
| 5/5 | Re-enable vsyscall support for x86_64arch/ arch/ arch/ +6 more | +105 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
Hey Andi,
First let me apologize, I've been busy with other things and
its been far too long since I last posted this. Anyway, I found some time to resync my trees and wanted to send this along.
You had asked earlier about performance impact:
Vanilla TSC:
149 nsecs per gtod call
367 nsecs per CLOCK_MONOTONIC call
288 nsecs per CLOCK_REALTIME call
Vanilla ACPI PM:
1272 nsecs per gtod call
1335 nsecs per CLOCK_MONOTONIC call
1273 nsecs per CLOCK_REALTIME call
GENERIC_TIME TSC:
149 nsecs per gtod call
304 nsecs per CLOCK_MONOTONIC call
275 nsecs per CLOCK_REALTIME callGENERIC_TIME ACPI PM:
1273 nsecs per gtod call
1275 nsecs per CLOCK_MONOTONIC call
1273 nsecs per CLOCK_REALTIME call
So almost no performance change.
Ingo has a few cleanups I need to merge, but otherwise I think this is getting close to ready for inclusion into -mm for testing. Please let me know if you have any major objections and if not I'll re-diff it against -mm and send it to Andrew.
New in the current C7 release:
o Synched up w/ 2.6.19-rc6-git11
o Reworked the patch order to be a bit more logical
o Dropped the apic_runs_main_timer removal on Andi's request
Let me know if you have any thoughts or comments!
thanks again!
-john