Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1716570 > unrolled thread
| Started by | Jiri Olsa <jolsa@redhat.com> |
|---|---|
| First post | 2017-08-21 16:50 +0200 |
| Last post | 2017-08-21 16:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: pmu::read() called erroneously in v4.13-rc{3,4} Jiri Olsa <jolsa@redhat.com> - 2017-08-21 16:50 +0200
| From | Jiri Olsa <jolsa@redhat.com> |
|---|---|
| Date | 2017-08-21 16:50 +0200 |
| Subject | Re: pmu::read() called erroneously in v4.13-rc{3,4} |
| Message-ID | <ugWbF-5BL-29@gated-at.bofh.it> |
On Fri, Aug 11, 2017 at 12:18:07PM +0100, Mark Rutland wrote: SNIP > > I'm also confused by perf_output_read_group() when event == leader. > AFAICT, in that case we won't read() the event at all, and we'll only > read() the siblings. Is that right? I think we assume perf_output_read_group is only called from event's PMI which means it's already been called for event jirka
Back to top | Article view | linux.kernel
csiph-web