public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] perf tools: Add a new generic section in perf.data
Date: Fri, 16 Oct 2009 09:10:46 +0200	[thread overview]
Message-ID: <20091016071046.GD20388@elte.hu> (raw)
In-Reply-To: <1255641017-13958-1-git-send-email-fweisbec@gmail.com>


* Frederic Weisbecker <fweisbec@gmail.com> wrote:

> +/*
> + * Version 0: contains trace_info section only
> + */
> +struct perf_file_additionals {
> +	u64				version;
> +	struct perf_file_section	trace_info;
> +};

i dont disagree with the change - but it would be even nicer to simply 
define a features bitmask, instead of a flat version - and add the 
trace_info section as a feature.

That way it's all a lot more manageable: we dont know about versions per 
se, we know about features. Individual features could be developed (and 
backported) in a distributed way - without having to worry about a flat 
version model.

So i'd suggest something like a bitmask in the perf.data file header:

	DECLARE_BITMAP(features, 256);

Plus every perf version knows about the features it supports:

	DECLARE_BITMAP(features_supported, 256);

The compatibility rule is: perf only touches attributes that belong to 
features it knows about.

	Ingo

  reply	other threads:[~2009-10-16  7:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-15 21:10 [PATCH] perf tools: Add a new generic section in perf.data Frederic Weisbecker
2009-10-16  7:10 ` Ingo Molnar [this message]
2009-10-16  7:33   ` Frederic Weisbecker
2009-10-16  7:42     ` Ingo Molnar
2009-10-17 15:12       ` [PATCH 1/2] perf tools: Use kernel bitmap library Frederic Weisbecker
2009-10-19  7:55         ` [tip:perf/core] " tip-bot for Frederic Weisbecker
2009-10-17 15:12       ` [PATCH 2/2] perf tools: Introduce bitmask'ed additional headers Frederic Weisbecker
2009-10-19  7:56         ` [tip:perf/core] " tip-bot for Frederic Weisbecker
2009-10-17 15:57       ` [PATCH 3/2] perf tools: Use DECLARE_BITMAP instead of an open-coded array Frederic Weisbecker
2009-10-17 16:03         ` Frederic Weisbecker
2009-10-19  7:30           ` Ingo Molnar
2009-10-19 19:40             ` Frederic Weisbecker
2009-10-19  7:56         ` [tip:perf/core] " tip-bot for Frederic Weisbecker

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=20091016071046.GD20388@elte.hu \
    --to=mingo@elte.hu \
    --cc=acme@redhat.com \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    /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