linux-kernel - Re: collecting static data related to tracing

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: <1274256931.3874.3.camel@jlt3.sipsolutions.net>
Date:	Wed, 19 May 2010 10:15:31 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	rostedt@...dmis.org, linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: collecting static data related to tracing

On Wed, 2010-05-19 at 09:28 +0200, Frederic Weisbecker wrote:

> > Sounds good, although it does require that I tell people who want to
> > record to also install the recording plugin, but that should be
> > manageable :) I can just dig out the data from the regular debugfs once
> > I add files containing it.

> This is a place where events injection might be suitable perhaps.
> Either kernel or user space event injection.
> 
> kernel space injection would be a simple trace event declared that
> have a callback called when it gets enabled. This callback would
> inject any events it wants.

Indeed, that is a good point, and it would also allow us to handle
hotplugging with the same event by sending it when a new device shows
up, and additionally when it is enabled to dump the current state.

johannes

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