From: john stultz <johnstul@us.ibm.com>
To: ak@suse.de
Cc: john stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] x86_64: Generic timekeeping for x86_64
Date: Wed, 6 Sep 2006 20:18:43 -0600 [thread overview]
Message-ID: <20060907021820.31476.17484.sendpatchset@localhost> (raw)
Hey Andi,
Just wanted to send this second pass on the x86_64 generic
timekeeping conversion. It includes a number of changes you suggested,
however its possible I missed a few things. I've made sure the patchset
compiles at each stage, and atleast w/ the box I was using it booted
each step as well.
Still on the TODO:
o See about merging i386/x86-64 hpet.c (maybe driver/char/hpet.c as
well?)
o 64bit hpet (should be trivial)
o Further cleanups
If anyone else is interested here, my full timekeeping tree can be
found here: http://sr71.net/~jstultz/tod/
New in the current C6 release:
o x86-64 cleanups
o arch-trivial patch that converts arches w/o inter-tick resolution
o ia64 fixups by Peter Keilty
Let me know if you have any thoughts or comments!
thanks again!
-john
next reply other threads:[~2006-09-07 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 2:18 john stultz [this message]
2006-09-07 2:18 ` [PATCH 1/6] x86_64: Enable arch-generic vsyscall support john stultz
2006-09-07 2:18 ` [PATCH 2/6] x86_64: hpet_address cleanup john stultz
2006-09-07 2:19 ` [PATCH 3/6] x86_64: Remove apic_runs_main_timer john stultz
2006-09-07 2:19 ` [PATCH 4/6] x86_64: Enable CONFIG_GENERIC_TIME john stultz
2006-09-07 2:19 ` [PATCH 5/6] x86_64: Clocksources for x86-64 john stultz
2006-09-07 2:19 ` [PATCH 6/6] x86_64: GENERIC_TIME based vsyscall code john stultz
2006-09-09 20:30 ` [PATCH 0/6] x86_64: Generic timekeeping for x86_64 Andi Kleen
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=20060907021820.31476.17484.sendpatchset@localhost \
--to=johnstul@us.ibm.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.