[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AA5AE29.6020107@cn.fujitsu.com>
Date: Tue, 08 Sep 2009 09:06:49 +0800
From: Li Zefan <lizf@...fujitsu.com>
To: Frederic Weisbecker <fweisbec@...il.com>
CC: Ingo Molnar <mingo@...e.hu>, Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Tom Zanussi <tzanussi@...il.com>,
Jason Baron <jbaron@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/6] perf trace: Add filter support
>> An example:
>>
>> #./perf record -f -e irq:irq_handler_entry:irq==18:record
>> or
>> #./perf record -f -e irq:irq_handler_entry:irq==18 -R
>> ^C
>
> We may want to write complex filters. While looking at this patchset,
> that seems possible this way, but the raw line may become unreadable:
>
> perf record -f -e irq:irq_handler_entry:"irq==18 && (name == 'foo' || bar == 'blah')":record
>
> May be we should add an option to let one also set the filters seperately then
> we could do:
>
> perf record -f -e -R irq:irq_handler_entry --filter "irq==18 && (name == 'foo' || bar == 'blah')"
>
I had the same idea. ;)
But using this option, is it possible to specify different filters
for different events? like this:
perf record -f -e -R irq:irq_handler_entry --filter "irq==18"
-e irq:softirq_entry --filter "vec==1"
--
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/
Powered by blists - more mailing lists