From: tip-bot for Stefani Seibold <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, luto@amacapital.net, hpa@zytor.com,
mingo@kernel.org, stefani@seibold.net, tglx@linutronix.de,
hpa@linux.intel.com
Subject: [tip:x86/vdso] x86, vdso: Revamp vclock_gettime.c
Date: Wed, 5 Mar 2014 14:30:56 -0800 [thread overview]
Message-ID: <tip-20dd4e23a10764f886c2a615bdc1f0c7db991cdb@git.kernel.org> (raw)
In-Reply-To: <1393881143-3569-4-git-send-email-stefani@seibold.net>
Commit-ID: 20dd4e23a10764f886c2a615bdc1f0c7db991cdb
Gitweb: http://git.kernel.org/tip/20dd4e23a10764f886c2a615bdc1f0c7db991cdb
Author: Stefani Seibold <stefani@seibold.net>
AuthorDate: Mon, 3 Mar 2014 22:12:14 +0100
Committer: H. Peter Anvin <hpa@linux.intel.com>
CommitDate: Wed, 5 Mar 2014 14:02:37 -0800
x86, vdso: Revamp vclock_gettime.c
This intermediate patch revamps the vclock_gettime.c by moving some functions
around. It is only for spliting purpose, to make whole the 32 bit vdso timer
patch easier to review.
Reviewed-by: Andy Lutomirski <luto@amacapital.net>
Signed-off-by: Stefani Seibold <stefani@seibold.net>
Link: http://lkml.kernel.org/r/1393881143-3569-4-git-send-email-stefani@seibold.net
Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
---
arch/x86/vdso/vclock_gettime.c | 85 +++++++++++++++++++++---------------------
1 file changed, 42 insertions(+), 43 deletions(-)
diff --git a/arch/x86/vdso/vclock_gettime.c b/arch/x86/vdso/vclock_gettime.c
index eb5d7a5..bbc8065 100644
--- a/arch/x86/vdso/vclock_gettime.c
+++ b/arch/x86/vdso/vclock_gettime.c
@@ -26,41 +26,26 @@
#define gtod (&VVAR(vsyscall_gtod_data))
-notrace static cycle_t vread_tsc(void)
+static notrace cycle_t vread_hpet(void)
{
- cycle_t ret;
- u64 last;
-
- /*
- * Empirically, a fence (of type that depends on the CPU)
- * before rdtsc is enough to ensure that rdtsc is ordered
- * with respect to loads. The various CPU manuals are unclear
- * as to whether rdtsc can be reordered with later loads,
- * but no one has ever seen it happen.
- */
- rdtsc_barrier();
- ret = (cycle_t)vget_cycles();
-
- last = VVAR(vsyscall_gtod_data).clock.cycle_last;
-
- if (likely(ret >= last))
- return ret;
+ return readl((const void __iomem *)fix_to_virt(VSYSCALL_HPET) + HPET_COUNTER);
+}
- /*
- * GCC likes to generate cmov here, but this branch is extremely
- * predictable (it's just a funciton of time and the likely is
- * very likely) and there's a data dependence, so force GCC
- * to generate a branch instead. I don't barrier() because
- * we don't actually need a barrier, and if this function
- * ever gets inlined it will generate worse code.
- */
- asm volatile ("");
- return last;
+notrace static long vdso_fallback_gettime(long clock, struct timespec *ts)
+{
+ long ret;
+ asm("syscall" : "=a" (ret) :
+ "0" (__NR_clock_gettime), "D" (clock), "S" (ts) : "memory");
+ return ret;
}
-static notrace cycle_t vread_hpet(void)
+notrace static long vdso_fallback_gtod(struct timeval *tv, struct timezone *tz)
{
- return readl((const void __iomem *)fix_to_virt(VSYSCALL_HPET) + HPET_COUNTER);
+ long ret;
+
+ asm("syscall" : "=a" (ret) :
+ "0" (__NR_gettimeofday), "D" (tv), "S" (tz) : "memory");
+ return ret;
}
#ifdef CONFIG_PARAVIRT_CLOCK
@@ -133,23 +118,37 @@ static notrace cycle_t vread_pvclock(int *mode)
}
#endif
-notrace static long vdso_fallback_gettime(long clock, struct timespec *ts)
+notrace static cycle_t vread_tsc(void)
{
- long ret;
- asm("syscall" : "=a" (ret) :
- "0" (__NR_clock_gettime),"D" (clock), "S" (ts) : "memory");
- return ret;
-}
+ cycle_t ret;
+ u64 last;
-notrace static long vdso_fallback_gtod(struct timeval *tv, struct timezone *tz)
-{
- long ret;
+ /*
+ * Empirically, a fence (of type that depends on the CPU)
+ * before rdtsc is enough to ensure that rdtsc is ordered
+ * with respect to loads. The various CPU manuals are unclear
+ * as to whether rdtsc can be reordered with later loads,
+ * but no one has ever seen it happen.
+ */
+ rdtsc_barrier();
+ ret = (cycle_t)vget_cycles();
- asm("syscall" : "=a" (ret) :
- "0" (__NR_gettimeofday), "D" (tv), "S" (tz) : "memory");
- return ret;
-}
+ last = VVAR(vsyscall_gtod_data).clock.cycle_last;
+ if (likely(ret >= last))
+ return ret;
+
+ /*
+ * GCC likes to generate cmov here, but this branch is extremely
+ * predictable (it's just a funciton of time and the likely is
+ * very likely) and there's a data dependence, so force GCC
+ * to generate a branch instead. I don't barrier() because
+ * we don't actually need a barrier, and if this function
+ * ever gets inlined it will generate worse code.
+ */
+ asm volatile ("");
+ return last;
+}
notrace static inline u64 vgetsns(int *mode)
{
next prev parent reply other threads:[~2014-03-05 22:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-03 21:12 [PATCH v22 00/12] Add 32 bit VDSO time function support Stefani Seibold
2014-03-03 21:12 ` [Patch v22 01/12] x86: Make vsyscall_gtod_data handling x86 generic Stefani Seibold
2014-03-05 22:30 ` [tip:x86/vdso] x86, vdso: " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 02/12] x86: Add new func _install_special_mapping() to mmap.c Stefani Seibold
2014-03-05 22:30 ` [tip:x86/vdso] mm: " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 03/12] x86: revamp vclock_gettime.c Stefani Seibold
2014-03-05 22:30 ` tip-bot for Stefani Seibold [this message]
2014-03-03 21:12 ` [Patch v22 04/12] x86: vclock_gettime.c __vdso_clock_gettime cleanup Stefani Seibold
2014-03-05 22:31 ` [tip:x86/vdso] x86, vdso: __vdso_clock_gettime() cleanup tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 05/12] x86: replace VVAR(vsyscall_gtod_data) by gtod macro Stefani Seibold
2014-03-05 22:31 ` [tip:x86/vdso] x86, vdso: Replace " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 06/12] x86: cleanup __vdso_gettimeofday Stefani Seibold
2014-03-05 22:31 ` [tip:x86/vdso] x86, vdso: Cleanup __vdso_gettimeofday() tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 07/12] x86: introduce VVAR marco for vdso32 Stefani Seibold
2014-03-05 22:31 ` [tip:x86/vdso] x86, vdso: Introduce " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 08/12] x86: Patch alternatives in the 32-bit vDSO Stefani Seibold
2014-03-05 22:31 ` [tip:x86/vdso] x86, vdso: Patch alternatives in the 32-bit VDSO tip-bot for Andy Lutomirski
2014-03-03 21:12 ` [Patch v22 09/12] x86: Add 32 bit VDSO time support for 32 bit kernel Stefani Seibold
2014-03-05 22:32 ` [tip:x86/vdso] x86, vdso: " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 10/12] x86: Add 32 bit VDSO time support for 64 " Stefani Seibold
2014-03-05 22:32 ` [tip:x86/vdso] x86, vdso: " tip-bot for Stefani Seibold
2014-03-03 21:12 ` [Patch v22 12/12] x86: Zero-pad the VVAR page Stefani Seibold
2014-03-05 22:32 ` [tip:x86/vdso] x86, vdso: " tip-bot for Andy Lutomirski
2014-03-06 17:51 ` [tip:x86/vdso] x86, vdso32: Disable stack protector, adjust optimizations tip-bot for H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2014-03-17 22:22 [PATCH v23 03/13] x86, vdso: Revamp vclock_gettime.c Stefani Seibold
2014-03-18 21:28 ` [tip:x86/vdso] " tip-bot for Stefani Seibold
2014-02-16 21:52 [PATCH v18 03/10] revamp vclock_gettime.c Stefani Seibold
2014-02-17 0:52 ` [tip:x86/vdso] x86, vdso: Revamp vclock_gettime.c tip-bot for Stefani Seibold
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=tip-20dd4e23a10764f886c2a615bdc1f0c7db991cdb@git.kernel.org \
--to=tipbot@zytor.com \
--cc=hpa@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=stefani@seibold.net \
--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