Messages in this thread |  | | | Date | Mon, 25 Jan 2010 23:47:40 +0900 | | Subject | Re: [PATCH 12/12] Revert "perf record: Intercept all events" | | From | Hitoshi Mitake <> |
| |
On Mon, Jan 25, 2010 at 11:23, Arnaldo Carvalho de Melo <acme@infradead.org> wrote: > Em Fri, Jan 22, 2010 at 10:39:13PM +0900, Hitoshi Mitake escreveu: >> This reverts commit f5a2c3dce03621b55f84496f58adc2d1a87ca16f. >> >> This patch is required for making "perf lock rec" work. >> The commit f5a2c3dce0 changes write_event() of builtin-record.c . >> And changed write_event() sometimes doesn't stop with perf lock rec. >> >> I'm researching what makes write_event() loop infinity, >> and noticed that there are some events with event_t->header.size == 0. >> But the detail of the problem, >> like kind of these events, isn't clear... >> >> If you know something related to this problem, >> could you tell me, Arnaldo? > > Well, this will have to wait for somebody to remove the need for > intercepting those events, reverting this patch fixes your tool while > breaking others that then won't catch all the events.
Yes, this patch is too egoistic thing and temporary solution. I have to consider and modify 'perf lock'.
> > I'll get 'perf regtest' out with some initial tests then try to get some > proposal for injecting the buildid, if found in a DSO, via > PERF_RECORD_MMAP, lets see how this goes...
What does "DSO" mean? Sorry, I'm not good at English...
> > Best Regards, > > - Arnaldo > > BTW: I took longer to send a response to this question addressed to me > because I wasn't on the CC list :-) > >
Oh, sorry... I wonder why I didn't add you to Cc or To :( It is completely my mistake, and thanks for your reply!
Thanks Hitoshi
|  |