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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Mon, 22 Oct 2012 12:02:48 +0100
From:	Pádraig Brady <P@...igBrady.com>
To:	abhishek agarwal <abhigem.126@...il.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [Perf] Adding timeout option

On 10/21/2012 05:18 AM, abhishek agarwal wrote:

> 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

 > sleep does not offer a good timeout resolution and it is not a good
 > option (according to me) either.

sleep was just following on the command example.
timeout(1) supports subsecond resolution,
through timer_create (CLOCK_REALTIME...) and
timeout indication through signals.

thanks,
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ