From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: Jens Axboe <jaxboe@fusionio.com>
Cc: fio mailing list <fio@vger.kernel.org>
Subject: Re: Build issue on arm: undefined reference to `get_cpu_clock'
Date: Thu, 12 Aug 2010 11:04:47 +0200 [thread overview]
Message-ID: <4C63B92F.3000009@free-electrons.com> (raw)
In-Reply-To: <4C6194C8.2090405@fusionio.com>
Hi Jens,
On 08/10/2010 08:04 PM, Jens Axboe wrote:
> On 08/10/2010 08:11 AM, Michael Opdenacker wrote:
>> The get_cpu_clock function is only defined in
>> arch/arch-ia64.h
>> arch/arch-x86.h
>> arch/arch-x86_64.h
>>
>> How are other architectures supported? I don't understand fio can
>> support them without defining the get_cpu_clock() function.
>>
>> I did my tests on version 1.42, but faced the same issues with the
>> latest git version.
>>
> Indeed, dunno what happened there. I'll take a look.
>
I have seen your addition of get_cpu_clock() for the ppc architecture.
By the way, wouldn't it be more portable to use the POSIX
clock_gettime() function instead of reading an architecture dependent
register? At least, this is recommended on
http://en.wikipedia.org/wiki/Time_Stamp_Counter
Thank you for your support,
Cheers,
Michael.
--
Michael Opdenacker, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
+ 33 621 604 642
next prev parent reply other threads:[~2010-08-12 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 12:11 Build issue on arm: undefined reference to `get_cpu_clock' Michael Opdenacker
2010-08-10 18:04 ` Jens Axboe
2010-08-12 9:04 ` Michael Opdenacker [this message]
2010-08-12 11:49 ` Jens Axboe
2010-08-15 19:03 ` Jens Axboe
2010-08-16 12:59 ` Michael Opdenacker
2010-08-16 22:27 ` Jens Axboe
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=4C63B92F.3000009@free-electrons.com \
--to=michael.opdenacker@free-electrons.com \
--cc=fio@vger.kernel.org \
--cc=jaxboe@fusionio.com \
/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