From: David Mosberger <davidm@napali.hpl.hp.com>
To: Hironobu Ishii <ishii.hironobu@jp.fujitsu.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
linux-ia64 <linux-ia64@vger.kernel.org>
Subject: Re: [RFC/PATCH, 3/4] readX_check() performance evaluation
Date: Wed, 28 Jan 2004 15:42:54 +0000 [thread overview]
Message-ID: <16407.55422.229863.840323@napali.hpl.hp.com> (raw)
In-Reply-To: <00a401c3e541$c1d347f0$2987110a@lsd.css.fujitsu.com>
>>>>> On Wed, 28 Jan 2004 10:54:42 +0900, Hironobu Ishii <ishii.hironobu@jp.fujitsu.com> said:
Hironobu> This is a patch for rawread 1.0.3.
Hironobu> Original rawread 1.0.3 depends on i386.
Hironobu> --- rawread.c.old 2004-01-22 19:33:43.000000000 +0900
Hironobu> +++ rawread.c 2004-01-27 23:26:24.406717936 +0900
Hironobu> @@ -94,8 +94,14 @@
Hironobu> __inline__ unsigned long long int rdtsc()
Hironobu> {
Hironobu> - unsigned long long int x;
Hironobu> - __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
Hironobu> + unsigned long long int x;
Hironobu> +#if __i386__
Hironobu> + __asm__ volatile (".byte 0x0f, 0x31" : "=A" (x));
Hironobu> +#elif __ia64__
Hironobu> + __asm__ volatile ("mov r8 = ar44");
Hironobu> +#else
Hironobu> + #error "Please write your own rdtsc()"
Hironobu> +#endif
Hironobu> return x;
Hironobu> }
Inline assembly doesn't work with the Intel compiler on ia64. I
suggest to use ia64_get_itc() defined in <asm/delay.h> instead.
--david
prev parent reply other threads:[~2004-01-28 15:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 1:54 [RFC/PATCH, 3/4] readX_check() performance evaluation Hironobu Ishii
2004-01-28 15:42 ` David Mosberger [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=16407.55422.229863.840323@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox