linux-kernel - Re: Linux wireless GSoC 2010 project ideas

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: <20100309224347.GD5058@nowhere>
Date:	Tue, 9 Mar 2010 23:43:52 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Till Kamppeter <till.kamppeter@...il.com>
Cc:	"Luis R. Rodriguez" <mcgrof@...il.com>,
	linux-wireless <linux-wireless@...r.kernel.org>,
	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org,
	lsb-discuss@...ts.linux-foundation.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Linux wireless GSoC 2010 project ideas

On Fri, Jan 29, 2010 at 12:51:59AM +0100, Till Kamppeter wrote:
> No problem for students to suggest topics. We are not restricted to  
> wireless in terms of kernel. We support kernel projects in general.
>
> Please give your suggestion as answer to this e-mail, doing "Reply to  
> all", as I am not a kernel export, the other participants of this thread  
> should have a look at the student's project ideas and help finding 
> mentors.
>
>    Till



Ok, I hope it's not too late.
Here is one subject that I would like to apply for:


= Improving tracing in perf events / ftrace =


Using trace events under perf events is still a young feature
and needs various improvements.

- Syscall events can carry only raw values and addresses.
We need to make them "aware" of strings and structures contents
from userspace.

- Make function / function graph tracers usable by perf

- Optimize tracing fast-path

- Improve perf tools to better handle trace events scalability

- Provide new perf tools that exploit trace events (scheduler
  migration analysis, etc...)

- Implement a per context excluding (eg: exclude irqs, exclude functions, etc...)

- There are always things to do there.


Of course, each of these elements require a lot of work,
so not all of them can be done in two months, and some
of them can be started already before the summer.

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