linux-kernel - Re: [PATCH 1/3] perf/e6500: Make event translations available in sysfs

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150218205603.GA21074@gmail.com>
Date:	Wed, 18 Feb 2015 21:56:03 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Scott Wood <scottwood@...escale.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Tom Huynh <tom.huynh@...escale.com>,
	Peter Zijlstra <peterz@...radead.org>,
	linuxppc-dev@...ts.ozlabs.org, acme@...nel.org,
	linux-kernel@...r.kernel.org, paulus@...ba.org,
	Jiri Olsa <jolsa@...hat.com>, mingo@...hat.com
Subject: Re: [PATCH 1/3] perf/e6500: Make event translations available in
 sysfs


* Scott Wood <scottwood@...escale.com> wrote:

> On Mon, 2015-02-09 at 21:40 +0100, Andi Kleen wrote:
> > > I'll NAK any external 'download area' (and I told that Andi 
> > > before): tools/perf/event-tables/ or so is a good enough 
> > > 'download area' with fast enough update cycles.
> > 
> > The proposal was to put it on kernel.org, similar to how
> > external firmware blobs are distributed. [...]

Fortunately perf is not an external firmware blob ...

> > [...] CPU event lists are data sheets, so are like 
> > firmware. [...]

What an absolute, idiotic, nonsense argument!

CPU event lists are human readable descriptions for events. 
If they aren't then they have no place in tooling.

Treating them like firmware is as backwards as it gets.

> > [...]  They do not follow the normal kernel code 
> > licenses. They are not source code. They cannot be 
> > reviewed in the normal way.
> 
> How is it different from describing registers and bits in 
> driver header files?  What does it mean to talk about a 
> license on information, rather than the expression of 
> information?

Andi is making idiotic arguments, instead of implementing 
the technically sane solution.

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/