Re: [PATCH] perf record: Allow passing perf's own pid to '--filter'

[Arnaldo Carvalho de Melo]

Em Mon, Jul 06, 2015 at 11:00:10PM +0800, pi3orama escreveu:
> åèæç iPhone
 
> > å 2015å7æ6æïäå9:56ïArnaldo Carvalho de Melo <acme@xxxxxxxxxx> åéï
> > I.e. having something in the filter expression that gets transformed
> > into the tools' pid, I have no problem with that, just curious about
> > what would be the best character to signal that a substitution needs to
> > be performed, if it is really '@VAR', as my first selection would be
> > '$VAR',
 
> $ has special meaning for shell. Using $ in cmdline require users use escaping or '' quoted string. Therefore I believe @ should be better. What do you think?

Yeah, that gets in the way, as it gets in the way for '!', i.e.
negating, and even tho, that is what is used in strace (and in 'perf
trace'):

  strace -e \!open,write ls

Or:

  strace -e '!open,write' ls

But apart from that, it would be good if expressions used in 'perf
probe' and here could have as much as possible the same semantics for
those markers, i.e. 'perf probe' already uses @ for some stuff, probably
the meaning is for "at", i.e. something at some place.

'$' strongly associated with variables, so I don't think it would be a
big problem to enclose expressions where variables (we may end having
others, no?)  in '', i.e.

  perf record -e sched:*switch --filter 'common_pid != $PERF_PID' -a

Doesn't look so ugly or cumbersome :-)

- Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/