Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1572543
| From | Mathieu Poirier <mathieu.poirier@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure |
| Date | 2017-02-02 18:40 +0100 |
| Message-ID | <t6twu-6ZQ-23@gated-at.bofh.it> (permalink) |
| References | (4 earlier) <t4ilQ-6Xe-25@gated-at.bofh.it> <t62wh-62p-13@gated-at.bofh.it> <t6aNc-37z-11@gated-at.bofh.it> <t6bpU-3E0-21@gated-at.bofh.it> <t6n7I-2Kl-1@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 2 February 2017 at 03:42, Alexander Shishkin <alexander.shishkin@linux.intel.com> wrote: > Mathieu Poirier <mathieu.poirier@linaro.org> writes: > >> Do we have two different syntax to specify the same behaviour? >> >> For example we have: >> >> --filter 'start 0x80082570/0x644' >> >> and >> >> --filter 'filter 0x80082570/0x644' >> >> Both will end up with filter->filter == 1 and filter->range == 1. > > This is another reason why enum action is needed. The difference between > 'start' and 'filter' is that the former means "start tracing when you > enter this region until something else stops it"; And what is the "something else here"? > the latter means > "trace only inside this region" (that is, start tracing when you branch > inside this region and stop when you branch outside). That is indeed how range filters work on CS. > They cannot be > treated interchangeably as I originally though. PT supports 'filter', CS > supports 'start', if I remember right. So we should make sure to > -EOPNOTSUPP things that we don't actually support. I already published slides at 2 conferences that uses "filter" for range filters. On CS I will have to continue using "filter" and "start" (when specified with a size element) as one and the same. > > Regards, > -- > Alex
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-02-01 13:50 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Mathieu Poirier <mathieu.poirier@linaro.org> - 2017-02-01 22:40 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Mathieu Poirier <mathieu.poirier@linaro.org> - 2017-02-01 23:20 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-02-02 11:50 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Mathieu Poirier <mathieu.poirier@linaro.org> - 2017-02-02 18:40 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2017-02-02 17:30 +0100
Re: [PATCH 1/3] perf, pt, coresight: Clean up address filter structure Mathieu Poirier <mathieu.poirier@linaro.org> - 2017-02-07 19:00 +0100
csiph-web