From: Andi Kleen <ak@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] x86_64: Generic timekeeping for x86_64
Date: Sat, 9 Sep 2006 22:30:49 +0200 [thread overview]
Message-ID: <200609092230.49943.ak@suse.de> (raw)
In-Reply-To: <20060907021820.31476.17484.sendpatchset@localhost>
On Thursday 07 September 2006 04:18, john stultz wrote:
> 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.
Looks all reasonable from a quick look.
I assume it will clash with the recent patch to remove wall_jiffies use,
but that should be easy to fix.
How does the performance of the user space gettimeofday look
compared to the old code in TSC mode?
BTW I got some experimental code to put clock_gettime into
user space too, but that can be later merged I guess.
-Andi
prev parent reply other threads:[~2006-09-09 21:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-07 2:18 [PATCH 0/6] x86_64: Generic timekeeping for x86_64 john stultz
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 ` Andi Kleen [this message]
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=200609092230.49943.ak@suse.de \
--to=ak@suse.de \
--cc=johnstul@us.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox