From: Andrea Arcangeli <andrea@suse.de>
To: john stultz <johnstul@us.ibm.com>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@elte.hu, Suleiman Souhlal <ssouhlal@FreeBSD.org>
Subject: rdtscp vgettimeofday
Date: Mon, 11 Dec 2006 01:39:04 +0100 [thread overview]
Message-ID: <20061211003904.GB5366@opteron.random> (raw)
In-Reply-To: <20061129025752.15379.14257.sendpatchset@localhost>
Hello,
As far as I can see, many changes happened but nobody has yet added
the rdtscp support to x86-64. rdtscp finally solves the problem and it
obsoletes hpet for timekeeping and it allows a fully userland
gettimeofday running at maximum speed in userland.
Before rdtscp we could never index the rdtsc offset in a proper index
without being in kernel with preemption disabled, so it could never
work reliably.
What's the status of the DSO API? Does it break backwards
compatibility or is the production glibc already capable of handling
that new kernel API?
I need rdtscp working on vsyscalls ASAP, but I should first understand
if I need to base my code on top of the vDSO patch or if to fork it
off in a dead branch to preserve backwards compatibility with current
glibc userland.
Thanks.
next prev parent reply other threads:[~2006-12-11 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 3:00 [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64 john stultz
2006-11-29 3:00 ` [PATCH 1/5][time][Generic] vsyscall-gtod support for GENERIC_TIME john stultz
2006-11-29 3:00 ` [PATCH 2/5][time][x86_64] hpet_address cleanup john stultz
2006-11-29 3:00 ` [PATCH 3/5][time][x86_64] Split x86_64/kernel/time.c up john stultz
2006-11-29 3:00 ` [PATCH 4/5][time][x86_64] Convert x86_64 to use GENERIC_TIME john stultz
2006-12-11 0:39 ` Andrea Arcangeli [this message]
2006-12-11 21:17 ` rdtscp vgettimeofday dean gaudet
2006-12-11 21:32 ` Andrea Arcangeli
2006-12-11 23:15 ` dean gaudet
2006-12-11 23:38 ` Andrea Arcangeli
2006-11-29 3:00 ` [PATCH 5/5][time][x86_64] Re-enable vsyscall support for x86_64 john stultz
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=20061211003904.GB5366@opteron.random \
--to=andrea@suse.de \
--cc=ak@suse.de \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ssouhlal@FreeBSD.org \
--cc=tglx@linutronix.de \
/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