From: Ingo Molnar <mingo@kernel.org>
To: Scott Wood <scottwood@freescale.com>
Cc: Tom Huynh <tom.huynh@freescale.com>,
Peter Zijlstra <peterz@infradead.org>,
Jiri Olsa <jolsa@redhat.com>,
linux-kernel@vger.kernel.org, acme@kernel.org,
Andi Kleen <andi@firstfloor.org>,
paulus@samba.org, linuxppc-dev@lists.ozlabs.org,
mingo@redhat.com
Subject: Re: [PATCH 1/3] perf/e6500: Make event translations available in sysfs
Date: Wed, 18 Feb 2015 21:56:03 +0100 [thread overview]
Message-ID: <20150218205603.GA21074@gmail.com> (raw)
In-Reply-To: <1423613998.2713.16.camel@aoeu.buserror.net>
* Scott Wood <scottwood@freescale.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
next prev parent reply other threads:[~2015-02-18 20:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-06 22:43 [PATCH 0/3] Add e6500 perf events to sysfs and update perf doc Tom Huynh
2015-02-06 22:43 ` [PATCH 1/3] perf/e6500: Make event translations available in sysfs Tom Huynh
2015-02-09 10:02 ` Peter Zijlstra
2015-02-09 10:07 ` Ingo Molnar
2015-02-09 12:11 ` Jiri Olsa
2015-02-09 13:25 ` Ingo Molnar
2015-02-09 20:40 ` Andi Kleen
2015-02-11 0:19 ` Scott Wood
2015-02-18 20:56 ` Ingo Molnar [this message]
2015-02-18 21:31 ` Andi Kleen
2015-02-16 16:10 ` Tom Huynh
2015-03-27 21:34 ` Kim Phillips
2015-03-28 0:32 ` Andi Kleen
2015-02-06 22:43 ` [PATCH 2/3] perf/e6500: Create a sysfs format entry for e6500 events Tom Huynh
2015-02-06 22:43 ` [PATCH 3/3] perf/doc: Update perf_event_attr struct Tom Huynh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150218205603.GA21074@gmail.com \
--to=mingo@kernel.org \
--cc=acme@kernel.org \
--cc=andi@firstfloor.org \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=scottwood@freescale.com \
--cc=tom.huynh@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).