linux-kernel - Re: [PATCH v4 3/3] tracing: Histogram for missed timer offsets

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: <20160830101527.3acd6ad6@gandalf.local.home>
Date:   Tue, 30 Aug 2016 10:15:27 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Binoy Jayan <binoy.jayan@...aro.org>
Cc:     Ingo Molnar <mingo@...hat.com>,
        Daniel Wagner <daniel.wagner@...-carit.de>,
        Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
        Masami <masami.hiramatsu@...aro.org>
Subject: Re: [PATCH v4 3/3] tracing: Histogram for missed timer offsets

On Tue, 30 Aug 2016 15:58:44 +0530
Binoy Jayan <binoy.jayan@...aro.org> wrote:

> +TRACE_EVENT(latency_hrtimer_interrupt,
> +
> +	TP_PROTO(long long toffset, struct task_struct *curr,
> +		struct task_struct *task),
> +
> +	TP_ARGS(toffset, curr, task),
> +
> +	TP_STRUCT__entry(
> +		__field(long long,	toffset)
> +		__array(char,		ccomm,	TASK_COMM_LEN)

Can curr be different than current? If not, lets not record it.

-- Steve


> +		__field(int,		cprio)
> +		__array(char,		tcomm,	TASK_COMM_LEN)
> +		__field(int,		tprio)
> +	),