linux-kernel - Re: [RFC PATCH] perf: Carve out cgroup-related code

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]

Date:	Wed, 11 May 2011 17:21:56 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Borislav Petkov <bp@...64.org>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH] perf: Carve out cgroup-related code


* Borislav Petkov <bp@...64.org> wrote:

> On Wed, May 11, 2011 at 10:13:42AM -0400, Ingo Molnar wrote:
> > 
> > * Borislav Petkov <bp@...64.org> wrote:
> > 
> > > On Wed, May 11, 2011 at 09:46:40AM -0400, Peter Zijlstra wrote:
> > > > On Wed, 2011-05-11 at 14:11 +0200, Borislav Petkov wrote:
> > > > >  include/linux/perf_event.h |  138 ++++++++++++-
> > > > 
> > > > I don't like exposing all that in a kernel wide header.. should we maybe
> > > > have kernel/events/internal.h?
> > > 
> > > Sounds prudent. Maybe add a patch ontop that moves all perf_event.h
> > > exports which are shared _only_ between kernel/events/*.c compilation
> > > units to an internal.h header? Ingo?
> > 
> > There's not that many that are in perf_event.h and are only used in 
> > kernel/event/core.c.
> > 
> > Below is a generated list of all exported functions and their usage sites. Out 
> > of 40 functions 7 should not be exported:
> > 
> >  __perf_sw_event()
> >  perf_swevent_put_recursion_context()
> >  perf_pmu_unregister()
> >  perf_output_copy()
> >  __perf_event_task_sched_in()
> >  __perf_event_task_sched_out()
> >  perf_event_read_value()
> 
> Right, but splitting perf_event.c further would cause a bunch more of them to 
> go up in the header since they're being shared among kernel/events/*.c files. 
> But in the end, this is a judgement call - I mean, even the polluting ones 
> have a clearly defined namespace starting their names with {_-,}perf_*. If 
> you asked me, I'd do an internal.h header from the get-go so that all is kept 
> as clean as possible.

We seem to be in wild agreement wrt. internal.h!

Thanks,

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