linux-kernel - Re: sched_clock

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BC73D02.5090108@petalogix.com>
Date:	Thu, 15 Apr 2010 18:21:22 +0200
From:	Michal Simek <michal.simek@...alogix.com>
To:	steve@...idescorp.com
CC:	Thomas Gleixner <tglx@...utronix.de>,
	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Wu Zhangjin <wuzhangjin@...il.com>
Subject: Re: sched_clock - microblaze

Steven J. Magnani wrote:
> Michal,
> 
> On Thu, 2010-04-15 at 16:55 +0200, Michal Simek wrote:
> 
>> Is unimplemented sched_clock the reason why ftrace not show fine grain time?
>>
>> Or is there any other thing which is wrong?
>>
> 
> I think that's it. On my platform we have a free-running 1 MHz counter
> so I implemented a platform sched_clock for that, and I get nice ftrace
> times.
> 
>  0) + 65.000 us   |  finish_task_switch();
>  0)               |  lock_sock_nested() {
>  0) + 52.000 us   |    local_bh_disable();
>  0) + 53.000 us   |    local_bh_enable();
>  0) ! 264.000 us  |  }

I don't understand why I should add any "new" free running counter 
because we have one free running counter which do it (clocksource timer 
- timer1). Or am I missing something?

Thanks for sending your code.
Michal



-- 
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/