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] [day] [month] [year] [list]
Date:	Sun, 8 Nov 2009 10:48:27 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	J K Rai <jk.anurag@...oo.com>, Mike Galbraith <efault@....de>,
	Frédéric Weisbecker 
	<fweisbec@...il.com>, Arnaldo Carvalho de Melo <acme@...hat.com>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: Instantaneous snapshot of CPU schedule


* J K Rai <jk.anurag@...oo.com> wrote:

> Hello
> 
> Is there any utility using which we can take current (instantaneous) 
> snapshot of process schedule on the linux based system from user land. 
> Like use a system call or command to know what is running on each of 
> the cpus 0..n-1 (assuming n cpus in the system). Output could be like 
> tuple (pid, cpu_no).
> 
> If such utility does not exist then kindly throw some light / ideas so 
> that it could be implemented.

We have a tool that can record scheduling events and analyze/display 
them, see:

  perf sched record

  perf sched latency
  perf sched map
  perf sched trace
  perf sched replay

the latest version is in:

  http://people.redhat.com/mingo/tip.git/README

do 'cd tools/perf; make -j install' to get the 'perf' command.

Now, your specific question was 'instantaneous'. I wouldnt mind such an 
extension to 'perf sched record':

  perf sched record --snapshot

or so. Then 'perf sched map' would show which task is running on which 
CPU. Other output modes would be possible too.

Would you be interested in extending 'perf sched' in such a fashion?

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ