linux-kernel - Re: [RFC PATCH 4/9] mce: Add persistent events

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: <1283352865.2356.29.camel@gandalf.stny.rr.com>
Date:	Wed, 01 Sep 2010 10:54:25 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Borislav Petkov <bp@...64.org>, acme@...radead.org,
	fweisbec@...il.com, linux-kernel@...r.kernel.org,
	Borislav Petkov <borislav.petkov@....com>
Subject: Re: [RFC PATCH 4/9] mce: Add persistent events

On Wed, 2010-09-01 at 08:14 +0200, Ingo Molnar wrote:

> More generally i agree with you that better modularization helps - a 
> nice improvement in this area would be to do a kernel/perf_event/ 
> splitup: i.e. split kernel/perf_event.c (which is getting a tad big) 
> into:
> 
>   kernel/events/output.c
>   kernel/events/trace.c
>   kernel/events/core.c
>   kernel/events/syscall.c
>   kernel/events/persistent.c
> 
> Maybe even move hw_breakpoint.c there, etc. There's already various 
> wrappers in perf_event.c that could be split out of the core code to 
> increase modularity. Later on we could have a sysfs.c, etc.
> 
> Any taker for such a massive restructuring? :)

I'm willing to help out. Just need to get past all the confs I seemed to
be going to lately. I feel I'm traveling once a month. Of course my
recent vacations did not help any ;-)

-- Steve


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