From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>,
Chris Wright <chrisw@sous-sol.org>,
Arjan van de Ven <arjan@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [PATCH] x86-64 highres/dyntick support
Date: Sun, 06 May 2007 22:58:47 +0200 [thread overview]
Message-ID: <1178485128.31213.98.camel@localhost.localdomain> (raw)
I'm pleased to announce the first cut of the final x86_64
highres/dyntick support, which I did based on Chris Wright's patch set,
which is again based on Arjan van de Ven's initial work:
http://www.tglx.de/projects/hrtimers/2.6.21-git2-x86-64/patches-2.6.21-git2.patch.bz2
Broken out version:
http://www.tglx.de/projects/hrtimers/2.6.21-git2-x86-64/patches-2.6.21-git2.tar.bz2
It applies on top of 2.6.21-git2 and contains the following patches:
# Andi's x86_64 queue (already in -mm and pending mainline merges)
x86_64-2.6.21-git2.patch
# Outstanding fixups to highres/dyntick core and i386
# (-mm and mainline pending)
highres-dyntick-avoid-xtime-lock-contention.patch
acpi-keep-tsc-stable-when-lapic-timer-c2-ok-is-set.patch
clocksource-fix-resume-logic.patch
clockevents-fix-resume-logic.patch
# x86_64 dyntick support
x86-64-untangle-hpet-headers.patch
x86-64-drive-set-rtc-mss.patch
i386-move-pit-setup-to-i8253-h.patch
x86-64-remove-dead-code-tsc-c.patch
x86-64-convert-to-clockevents.patch
x86-64-prepare-idle-for-dyntick.patch
x86-64-enable-highres-dyntick.patch
The x86-64-convert-to-clockevents.patch is rather large, but there is no
way to do this incremental. The clockevents conversion has to be done in
one go.
The x86-64 clockevents patch set overall summary is:
22 files changed, 631 insertions(+), 1199 deletions(-)
due to sharing the code of PIT and HPET with i386.
I did not dare to tackle sharing apic.c yet, but there is definitely a
chance to get this done some day when I get bored and do a:
# mkdir arch/x86 :)
I'm going to post the x86_64 set for review to LKML once the outstanding
highres/dyntick fixups have hit mainline resp. -mm
To create a highres / dyntick enabled kernel for x86_64:
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.21.tar.bz2
http://kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.21-git2.bz2
http://www.tglx.de/projects/hrtimers/2.6.21-git2-x86-64/patches-2.6.21-git2.patch.bz2
Comments, bugreports, patches are welcome as ususal
Thanks,
tglx
next reply other threads:[~2007-05-06 20:56 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-06 20:58 Thomas Gleixner [this message]
2007-05-07 9:16 ` [PATCH] x86-64 highres/dyntick support Nicolas Mailhot
2007-05-07 15:28 ` Thomas Gleixner
2007-05-08 17:08 ` Nicolas Mailhot
2007-05-07 16:31 ` Chris Wright
2007-05-07 16:46 ` Thomas Gleixner
2007-05-07 17:18 ` Chris Wright
2007-05-08 9:39 ` Chris Wright
2007-05-08 9:42 ` [PATCH 1/5] x86_64: tsc compile fix Chris Wright
2007-05-08 9:47 ` Thomas Gleixner
2007-05-08 9:43 ` [PATCH 2/5] x86_64: __setup_APIC_LVTT whitespace fix Chris Wright
2007-05-08 9:48 ` Thomas Gleixner
2007-05-08 9:44 ` [PATCH 3/5] i386: hpet assumes boot cpu is 0 Chris Wright
2007-05-08 9:54 ` Thomas Gleixner
2007-05-08 9:46 ` [PATCH 4/5] i386: i8253 clockevent shutdown and unused using pit Chris Wright
2007-05-08 9:53 ` Thomas Gleixner
2007-05-08 9:47 ` [PATCH 5/5] x86_64: restore restore nohpet cmdline Chris Wright
2007-05-08 9:53 ` Thomas Gleixner
2007-05-08 9:51 ` [PATCH] x86-64 highres/dyntick support Thomas Gleixner
2007-05-08 9:51 ` Chris Wright
2007-05-08 9:58 ` Thomas Gleixner
2007-05-08 10:06 ` Chris Wright
2007-05-08 10:34 ` Thomas Gleixner
2007-05-08 13:15 ` Pallipadi, Venkatesh
2007-05-07 22:43 ` Venki Pallipadi
2007-05-07 23:15 ` Thomas Gleixner
2007-05-14 1:17 ` Alistair John Strachan
2007-05-14 6:33 ` Thomas Gleixner
2007-05-14 10:26 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v1 Thomas Gleixner
2007-05-14 20:10 ` Valdis.Kletnieks
2007-05-14 20:23 ` Thomas Gleixner
2007-05-14 21:15 ` Alistair John Strachan
2007-05-14 22:05 ` Thomas Gleixner
2007-05-14 22:42 ` Alistair John Strachan
2007-05-15 8:18 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v4 Thomas Gleixner
2007-05-15 14:06 ` Frank Sorenson
2007-05-15 21:53 ` Thomas Gleixner
2007-05-15 23:20 ` Frank Sorenson
2007-05-16 5:02 ` Frank Sorenson
2007-05-16 6:20 ` Thomas Gleixner
2007-05-16 9:01 ` Thomas Gleixner
2007-05-15 23:23 ` Alistair John Strachan
2007-05-16 5:54 ` Thomas Gleixner
2007-05-16 10:03 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v5 Thomas Gleixner
2007-05-16 19:48 ` Frank Sorenson
2007-05-17 4:25 ` Frank Sorenson
2007-05-17 19:12 ` Frank Sorenson
2007-05-17 19:19 ` Christoph Lameter
2007-05-18 3:55 ` Frank Sorenson
2007-05-18 16:58 ` Christoph Lameter
2007-05-18 19:44 ` Christoph Lameter
2007-05-17 22:09 ` [PATCH] x86-64 highres/dyntick support 2.6.22-rc1-v7 Thomas Gleixner
2007-05-21 1:14 ` Valdis.Kletnieks
-- strict thread matches above, loose matches on Subject: below --
2007-05-07 12:07 [PATCH] x86-64 highres/dyntick support Mats Johannesson
2007-05-07 15:13 ` Thomas Gleixner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1178485128.31213.98.camel@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=chrisw@sous-sol.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rostedt@goodmis.org \
--cc=venkatesh.pallipadi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox