linux-kernel - Re: [RFC PATCH] tracing: add sched_prio

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: <97c2c0d1-c815-2f5c-d1ae-925ee6904fb8@redhat.com>
Date:	Fri, 15 Jul 2016 14:46:33 -0300
From:	Daniel Bristot de Oliveira <bristot@...hat.com>
To:	Julien Desfossez <jdesfossez@...icios.com>,
	Steven Rostedt <rostedt@...dmis.org>
Cc:	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...nel.org>, daolivei@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH] tracing: add sched_prio_update

On 07/06/2016 10:53 AM, Julien Desfossez wrote:
>> But still, it's a
>> > rather hefty tracepoint (lots of fields), probably want to keep from
>> > adding comm too.
> Yes, I agree we can remove the comm field, it is easy to get from the
> previous sched_switch.
> 

Sorry for the delay. I do liked this tracepoint! about comm, I think
that having the comm will make the tracepoint easier to understand, so I
vote for maintain the comm field. But I also see Steven's point and I
would not complain if you more expert guys agree on removing comm :-).