linux-kernel - [PATCH] Add better resolution to initcall

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>] [day] [month] [year] [list]

Date:	Fri, 12 Sep 2008 12:51:45 -0700
From:	Tim Bird <tim.bird@...sony.com>
To:	linux-embedded <linux-embedded@...r.kernel.org>
CC:	linux kernel <linux-kernel@...r.kernel.org>
Subject: [PATCH]  Add better resolution to initcall_debug timings

Change the time resolution for initcall_debug to microseconds,
from milliseconds.  This is handy to determine which
initcalls you want to work on for faster booting.

One one of my test machines, over 90% of the initcalls are
less than a millisecond and (without this patch) these are
all reported as 0 msecs.  Working on the 900 us ones is more
important than the 4 us ones.

With 'quiet' on the kernel command line, this adds no significant
overhead to kernel boot time.

Signed-off-by: Tim Bird <tim.bird@...sony.com>
---
 init/main.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/init/main.c b/init/main.c
index bdc8be0..f441cad 100644
--- a/init/main.c
+++ b/init/main.c
@@ -719,8 +719,8 @@ int do_one_initcall(initcall_t fn)
 		delta = ktime_sub(t1, t0);

 		print_fn_descriptor_symbol("initcall %s", fn);
-		printk(" returned %d after %Ld msecs\n", result,
-			(unsigned long long) delta.tv64 >> 20);
+		printk(" returned %d after %Ld usecs\n", result,
+			(unsigned long long) delta.tv64 >> 10);
 	}

 	msgbuf[0] = 0;
-- 
1.5.6

--
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/