Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Michael Opdenacker <michael.opdenacker@free-electrons.com>
Cc: fio mailing list <fio@vger.kernel.org>
Subject: Re: Build issue on arm: undefined reference to `get_cpu_clock'
Date: Sun, 15 Aug 2010 15:03:37 -0400	[thread overview]
Message-ID: <4C683A09.6090303@fusionio.com> (raw)
In-Reply-To: <4C63DFE6.9000608@fusionio.com>

On 08/12/2010 07:49 AM, Jens Axboe wrote:
> On 08/12/2010 05:04 AM, Michael Opdenacker wrote:
>> 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
> 
> Of course using clock_gettime() would be more portable. The
> point of the CPU clock is speed. If you are testing IOPS into
> the ranges of millions and doing ~5 clock calls per IO, then
> portability takes a back seat to speed.
> 
> But arm needs to work of course, I will commit a patch to
> fix it as soon as I can.

Committed such a patch, would be nice if you could test.
Either git pull or download fio-1.43-rc1 (or latest snap).

-- 
Jens Axboe


  reply	other threads:[~2010-08-15 19:03 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
2010-08-12 11:49     ` Jens Axboe
2010-08-15 19:03       ` Jens Axboe [this message]
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=4C683A09.6090303@fusionio.com \
    --to=jaxboe@fusionio.com \
    --cc=fio@vger.kernel.org \
    --cc=michael.opdenacker@free-electrons.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