linux-kernel - Re: [tip:perf/core] perf: Update perf_event

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: <alpine.DEB.2.02.1307250832010.18434@pianoman.cluster.toy>
Date:	Thu, 25 Jul 2013 08:34:51 -0400 (EDT)
From:	Vince Weaver <vince@...ter.net>
To:	Adrian Hunter <adrian.hunter@...el.com>
cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	peterz@...radead.org, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf: Update perf_event_type documentation

On Thu, 25 Jul 2013, Adrian Hunter wrote:

> On 24/07/13 20:54, Vince Weaver wrote:
> > On Tue, 23 Jul 2013, tip-bot for Peter Zijlstra wrote:
> > 
> >> Commit-ID:  a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> >> Gitweb:     http://git.kernel.org/tip/a5cdd40c9877e9aba704c020fd65d26b5cfecf18
> >> Author:     Peter Zijlstra <peterz@...radead.org>
> >> AuthorDate: Tue, 16 Jul 2013 17:09:07 +0200
> >> Committer:  Ingo Molnar <mingo@...nel.org>
> >> CommitDate: Tue, 23 Jul 2013 12:17:08 +0200
> >>
> >> perf: Update perf_event_type documentation
> >>
> >> Due to a discussion with Adrian I had a good look at the perf_event_type record
> >> layout and found the documentation to be somewhat unclear.

> ...

> This is not the patch that adds new sample format bits.
> 
> New sample format bits are always backward compatible in the sense that the
> kernel perf_event_open system call will return an error if you try to use
> sample format bits that it does not know about.

Yes, I meant the addition of the sample_id fields to the existing sample 
values.  Though if Peter is right and those have always been there since 
the beginning and just not documented then that won't break anything.  
The commit message wasn't really as clear as it could be.

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