linux-kernel - Re: [tip:perf/core] perf tools, Alpha: Add Alpha support to perf.h

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: <20091026122247.GA31982@elte.hu>
Date:	Mon, 26 Oct 2009 13:22:47 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Pekka Enberg <penberg@...helsinki.fi>
Cc:	mingo@...hat.com, hpa@...or.com, paulus@...ba.org,
	linux-kernel@...r.kernel.org, a.p.zijlstra@...llo.nl,
	ink@...assic.park.msu.ru, tglx@...utronix.de, rth@...ddle.net,
	mcree@...on.net.nz, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf tools, Alpha: Add Alpha support to perf.h


* Pekka Enberg <penberg@...helsinki.fi> wrote:

> Hi Ingo,
> 
> On Mon, Oct 26, 2009 at 1:38 PM, tip-bot for Michael Cree
> <mcree@...on.net.nz> wrote:
> > Commit-ID:  fcd14b3203b538dca04a2b065c774c0b57863eec
> > Gitweb:     http://git.kernel.org/tip/fcd14b3203b538dca04a2b065c774c0b57863eec
> > Author:     Michael Cree <mcree@...on.net.nz>
> > AuthorDate: Mon, 26 Oct 2009 21:32:06 +1300
> > Committer:  Ingo Molnar <mingo@...e.hu>
> > CommitDate: Mon, 26 Oct 2009 09:45:41 +0100
> >
> > perf tools, Alpha: Add Alpha support to perf.h
> >
> > For the perf tool the patch implements an Alpha specific section
> > in the perf.h header file.
> >
> > Signed-off-by: Michael Cree <mcree@...on.net.nz>
> > Cc: Richard Henderson <rth@...ddle.net>
> > Cc: Ivan Kokshaysky <ink@...assic.park.msu.ru>
> > Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> > Cc: Paul Mackerras <paulus@...ba.org>
> > LKML-Reference: <1256545926-6972-1-git-send-email-mcree@...on.net.nz>
> > Signed-off-by: Ingo Molnar <mingo@...e.hu>
> > ---
> >  tools/perf/perf.h |    6 ++++++
> >  1 files changed, 6 insertions(+), 0 deletions(-)
> >
> > diff --git a/tools/perf/perf.h b/tools/perf/perf.h
> > index 8cc4623..216bdb2 100644
> > --- a/tools/perf/perf.h
> > +++ b/tools/perf/perf.h
> > @@ -47,6 +47,12 @@
> >  #define cpu_relax()    asm volatile("":::"memory")
> >  #endif
> >
> > +#ifdef __alpha__
> > +#include "../../arch/alpha/include/asm/unistd.h"
> > +#define rmb()          asm volatile("mb" ::: "memory")
> > +#define cpu_relax()    asm volatile("" ::: "memory")
> > +#endif
> 
> OK, I'll bite. We tell userspace developers not to include kernel 
> headers. Why is it okay for perf to do it (especially for something 
> that's in asm)?

The main counter-argument against inclusion was always "what if we break 
them accidentally". I.e. it can become a semi-ABI - stuff we cannot 
change because we cannot change the outside projects. With perf this 
cannot occur - it's all in one Git tree and can always be fixed/changed.

Note that we reuse a couple of other facilities in tools/perf as well - 
linux/list.h, rbtree.c, etc. - and this is good - you can code perf as 
if you were hacking on the kernel! ;-)

	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/