From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> To: Steven Rostedt <rostedt@goodmis.org>, linux-kernel@vger.kernel.org, linux-trace-devel@vger.kernel.org Cc: Arnaldo Carvalho de Melo <acme@kernel.org>, Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>, Andrew Morton <akpm@linux-foundation.org>, linux-mm@kvack.org, Jaewon Kim <jaewon31.kim@samsung.com>, Vlastimil Babka <vbabka@suse.cz>, Kees Cook <keescook@chromium.org> Subject: Re: [PATCH 0/3] tool lib traceevent: Fix some parsing errors Date: Wed, 17 Jun 2020 19:55:29 -0300 [thread overview] Message-ID: <656DB3D9-6D76-4103-B05B-8E4FE142C3B9@gmail.com> (raw) In-Reply-To: <20200617172804.7eccb845@oasis.local.home> On June 17, 2020 6:28:04 PM GMT-03:00, Steven Rostedt <rostedt@goodmis.org> wrote: >Hi Arnaldo, > >I guess these patches were missed. I'll pick those tomorrow, Thanks for the reminder, - Arnaldo > >-- Steve > > >On Tue, 24 Mar 2020 16:08:45 -0400 >Steven Rostedt <rostedt@goodmis.org> wrote: > >> Arnaldo, >> >> Here's a few patches for lib traceevent. >> >> The first one adds an "append()" helper function for appending to >strings, >> which will also simplify the next patch. >> >> The second patch handles "__attribute__((user))" in the field of a >> trace event. This is needed after the stack leak code added this >> to parameters of system call events. >> >> The last patch adds handling of __builtin_expect(), as someone wanted >> to move IS_ERR_VALUE() from the fast path into the print fmt section, >> which breaks the parsing. This should also be useful for other macros >> that may evaluate down to a __builtin_expect(). >> >> Steven Rostedt (VMware) (3): >> tools lib traceevent: Add append() function helper for >appending strings >> tools lib traceevent: Handle __attribute__((user)) in field >names >> tools lib traceevent: Add handler for __builtin_expect() >> >> ---- >> tools/lib/traceevent/event-parse.c | 168 >++++++++++++++++++++++++------------- >> 1 file changed, 111 insertions(+), 57 deletions(-) -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
WARNING: multiple messages have this Message-ID (diff)
From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com> To: Steven Rostedt <rostedt@goodmis.org>,linux-kernel@vger.kernel.org,linux-trace-devel@vger.kernel.org Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,Ingo Molnar <mingo@kernel.org>,Jiri Olsa <jolsa@redhat.com>,Namhyung Kim <namhyung@kernel.org>,Andrew Morton <akpm@linux-foundation.org>,linux-mm@kvack.org,Jaewon Kim <jaewon31.kim@samsung.com>,Vlastimil Babka <vbabka@suse.cz>,Kees Cook <keescook@chromium.org> Subject: Re: [PATCH 0/3] tool lib traceevent: Fix some parsing errors Date: Wed, 17 Jun 2020 19:55:29 -0300 [thread overview] Message-ID: <656DB3D9-6D76-4103-B05B-8E4FE142C3B9@gmail.com> (raw) In-Reply-To: <20200617172804.7eccb845@oasis.local.home> On June 17, 2020 6:28:04 PM GMT-03:00, Steven Rostedt <rostedt@goodmis.org> wrote: >Hi Arnaldo, > >I guess these patches were missed. I'll pick those tomorrow, Thanks for the reminder, - Arnaldo > >-- Steve > > >On Tue, 24 Mar 2020 16:08:45 -0400 >Steven Rostedt <rostedt@goodmis.org> wrote: > >> Arnaldo, >> >> Here's a few patches for lib traceevent. >> >> The first one adds an "append()" helper function for appending to >strings, >> which will also simplify the next patch. >> >> The second patch handles "__attribute__((user))" in the field of a >> trace event. This is needed after the stack leak code added this >> to parameters of system call events. >> >> The last patch adds handling of __builtin_expect(), as someone wanted >> to move IS_ERR_VALUE() from the fast path into the print fmt section, >> which breaks the parsing. This should also be useful for other macros >> that may evaluate down to a __builtin_expect(). >> >> Steven Rostedt (VMware) (3): >> tools lib traceevent: Add append() function helper for >appending strings >> tools lib traceevent: Handle __attribute__((user)) in field >names >> tools lib traceevent: Add handler for __builtin_expect() >> >> ---- >> tools/lib/traceevent/event-parse.c | 168 >++++++++++++++++++++++++------------- >> 1 file changed, 111 insertions(+), 57 deletions(-) -- Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-06-17 22:56 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-24 20:08 [PATCH 0/3] tool lib traceevent: Fix some parsing errors Steven Rostedt 2020-03-24 20:08 ` [PATCH 1/3] tools lib traceevent: Add append() function helper for appending strings Steven Rostedt 2020-03-24 20:08 ` [PATCH 2/3] tools lib traceevent: Handle __attribute__((user)) in field names Steven Rostedt 2020-03-24 20:08 ` [PATCH 3/3] tools lib traceevent: Add handler for __builtin_expect() Steven Rostedt 2020-06-17 21:28 ` [PATCH 0/3] tool lib traceevent: Fix some parsing errors Steven Rostedt 2020-06-17 22:55 ` Arnaldo Carvalho de Melo [this message] 2020-06-17 22:55 ` Arnaldo Carvalho de Melo 2020-06-18 13:24 ` Arnaldo Carvalho de Melo
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=656DB3D9-6D76-4103-B05B-8E4FE142C3B9@gmail.com \ --to=arnaldo.melo@gmail.com \ --cc=acme@kernel.org \ --cc=akpm@linux-foundation.org \ --cc=jaewon31.kim@samsung.com \ --cc=jolsa@redhat.com \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=linux-trace-devel@vger.kernel.org \ --cc=mingo@kernel.org \ --cc=namhyung@kernel.org \ --cc=rostedt@goodmis.org \ --cc=vbabka@suse.cz \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.