| 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
| ||
|
Message-ID: <CAMjzKwVn4Y+ocZ7Ud_CSM34KP=zO1N84ZApG1s6CG6onSP_x-g@mail.gmail.com> Date: Sun, 21 Oct 2012 09:48:09 +0530 From: abhishek agarwal <abhigem.126@...il.com> To: Pádraig Brady <P@...igbrady.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [Perf] Adding timeout option sleep does not offer a good timeout resolution and it is not a good option (according to me) either. perfmon had "timeout" option and i guess, same do oprofile. On Sat, Oct 20, 2012 at 1:58 AM, Pádraig Brady <P@...igbrady.com> wrote: > On 10/13/2012 08:54 AM, abhishek agarwal wrote: >> >> Hi folks.. >> >> I was thinking that why cant we have a timeout option in perf stat >> command. The timeout feature will help us to profile a process for a >> stipulated time (preferably in millisecs) and make perf stat return >> after that time. >> Eg: >> >> perf stat --timeout=10 sleep 100 >> >> This will make perf return and report stats after 10 ms... >> >> Hope anyone can shed some more light on the idea > > > It seems preferable to use the timeout program to do this. > Either sending a handled signal to the perf process like: > > timeout -s HUP 10 perf stat sleep 100 > > Or even better, just use that to kill the monitored process itself > > perf stat timeout 10 sleep 100 > > cheers, > Pádraig. -- 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