Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1386627
| From | Alexander Shishkin <alexander.shishkin@linux.intel.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v1 4/5] perf: Introduce address range filtering |
| Date | 2016-04-25 18:10 +0200 |
| Message-ID | <rrRfd-hZ-37@gated-at.bofh.it> (permalink) |
| References | <rqoRX-2Wv-3@gated-at.bofh.it> <rqoRY-2Wv-33@gated-at.bofh.it> <rqE0G-6O2-29@gated-at.bofh.it> <rqLYe-4HV-13@gated-at.bofh.it> <rrPwJ-7gP-7@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Peter Zijlstra <peterz@infradead.org> writes:
> On Fri, Apr 22, 2016 at 07:19:11PM +0300, Alexander Shishkin wrote:
>> /**
>> + * struct perf_addr_filter - address range filter definition
>> + * @entry: event's filter list linkage
>> + * @inode: object file's inode for file-based filters
>> + * @offset: filter range offset
>> + * @size: filter range size
>> + * @range: 1: range, 0: address
>> + * @filter: 1: filter/start, 0: stop
>> + * @kernel: 1: kernel, 0: file-based
>> + *
>> + * This is a hardware-agnostic filter configuration as specified by the user.
>> + */
>> +struct perf_addr_filter {
>> + struct list_head entry;
>> + struct inode *inode;
>> + unsigned long offset;
>> + unsigned long size;
>> + unsigned int range : 1,
>> + filter : 1,
>> + kernel : 1;
>> +};
>
> FWIW, why not have !inode be kernel?
It actually can, you're right.
Regards,
--
Alex
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-21 17:40 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-22 09:50 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-22 18:20 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 15:00 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-25 17:50 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 15:20 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 15:40 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-25 18:10 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 15:30 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-25 18:10 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 16:20 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-25 18:10 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Peter Zijlstra <peterz@infradead.org> - 2016-04-25 16:30 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-25 18:20 +0200
Re: [PATCH v1 4/5] perf: Introduce address range filtering Alexander Shishkin <alexander.shishkin@linux.intel.com> - 2016-04-26 16:40 +0200
csiph-web