From: Hironobu Ishii <ishii.hironobu@jp.fujitsu.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>
Subject: [RFC/PATCH, 3/4] readX_check() performance evaluation
Date: Wed, 28 Jan 2004 01:54:42 +0000 [thread overview]
Message-ID: <00a401c3e541$c1d347f0$2987110a@lsd.css.fujitsu.com> (raw)
This is a patch for rawread 1.0.3.
Original rawread 1.0.3 depends on i386.
Thanks,
Hironobu Ishii
--- rawread.c.old 2004-01-22 19:33:43.000000000 +0900
+++ rawread.c 2004-01-27 23:26:24.406717936 +0900
@@ -94,8 +94,14 @@
__inline__ unsigned long long int rdtsc()
{
- unsigned long long int x;
- __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
+ unsigned long long int x;
+#if __i386__
+ __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
+#elif __ia64__
+ __asm__ volatile ("mov r8 = ar44");
+#else
+ #error "Please write your own rdtsc()"
+#endif
return x;
}
WARNING: multiple messages have this Message-ID (diff)
From: Hironobu Ishii <ishii.hironobu@jp.fujitsu.com>
To: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>
Subject: [RFC/PATCH, 3/4] readX_check() performance evaluation
Date: Wed, 28 Jan 2004 10:54:42 +0900 [thread overview]
Message-ID: <00a401c3e541$c1d347f0$2987110a@lsd.css.fujitsu.com> (raw)
This is a patch for rawread 1.0.3.
Original rawread 1.0.3 depends on i386.
Thanks,
Hironobu Ishii
--- rawread.c.old 2004-01-22 19:33:43.000000000 +0900
+++ rawread.c 2004-01-27 23:26:24.406717936 +0900
@@ -94,8 +94,14 @@
__inline__ unsigned long long int rdtsc()
{
- unsigned long long int x;
- __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
+ unsigned long long int x;
+#if __i386__
+ __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
+#elif __ia64__
+ __asm__ volatile ("mov r8 = ar44");
+#else
+ #error "Please write your own rdtsc()"
+#endif
return x;
}
next reply other threads:[~2004-01-28 1:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 1:54 Hironobu Ishii [this message]
2004-01-28 1:54 ` [RFC/PATCH, 3/4] readX_check() performance evaluation Hironobu Ishii
2004-01-28 15:42 ` David Mosberger
2004-01-28 15:42 ` David Mosberger
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='00a401c3e541$c1d347f0$2987110a@lsd.css.fujitsu.com' \
--to=ishii.hironobu@jp.fujitsu.com \
--cc=linux-ia64@vger.kernel.org \
--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.