mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Michael Ellerman <michael@ellerman.id.au>
Cc: Peter Zijlstra <peterz@infradead.org>,
	acme@infradead.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org, rob@landley.net
Subject: Re: [RFC/PATCH] perf: Expand definition of sysfs format attribute
Date: Mon, 8 Apr 2013 17:51:56 +0200	[thread overview]
Message-ID: <20130408155156.GB1287@krava.redhat.com> (raw)
In-Reply-To: <20130408115749.GB17849@concordia>

On Mon, Apr 08, 2013 at 09:57:50PM +1000, Michael Ellerman wrote:

SNIP

> > 
> > ISTR discussing this with Jiri at some point.. I think we ended up with
> > being fine with overlapping ranges but having perf issue a warning (not
> > an error) when attributes of a single event have overlap.
> 
> OK great.
> 
> > I'm not sure the latter was ever implemented in the userspace side.
> 
> Yeah not that I can see with a quick look. It's fairly advanced usage
> IMHO so a warning would be nice, but not essential.

oops, missed this email.. sry

it should be ok to overlap.. we don't check those ranges in perf
tool now.. just take whatever is defined in format file

adding the warning to my todo list ;-)

jirka

  reply	other threads:[~2013-04-08 15:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-04  4:21 Michael Ellerman
2013-04-08  7:24 ` Michael Ellerman
2013-05-06  1:08   ` Michael Ellerman
2013-05-06  8:20     ` Arnaldo Carvalho de Melo
2013-05-06 11:36       ` Jiri Olsa
2013-04-08  9:05 ` Peter Zijlstra
2013-04-08 11:57   ` Michael Ellerman
2013-04-08 15:51     ` Jiri Olsa [this message]
2013-05-10 15:27 ` Peter Zijlstra

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=20130408155156.GB1287@krava.redhat.com \
    --to=jolsa@redhat.com \
    --cc=acme@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    --cc=peterz@infradead.org \
    --cc=rob@landley.net \
    /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

all inboxes | Powered by JetHome®