[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAM9d7ciRP17_YV5dtrphWKEXEzOTy7XQw7tG13oVs5RV3XzcYg@mail.gmail.com>
Date: Tue, 18 Mar 2014 23:26:53 +0900
From: Namhyung Kim <namhyung@...nel.org>
To: Jiri Olsa <jolsa@...hat.com>
Cc: Ramkumar Ramachandra <artagnon@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Steven Rostedt <rostedt@...dmis.org>,
Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH 5/5] perf test: squelch warnings about undefined sizeof
Hi Jiri,
On Tue, Mar 18, 2014 at 10:23 PM, Jiri Olsa <jolsa@...hat.com> wrote:
> On Tue, Mar 18, 2014 at 05:09:33PM +0900, Namhyung Kim wrote:
>> On Mon, 17 Mar 2014 18:26:38 -0400, Ramkumar Ramachandra wrote:
>> > perf test emits the following warnings on the parse events test:
>> >
>> > $ perf test
>> > 5: parse events tests
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > Warning: function sizeof not defined
>> > ...
>> >
>> > Squelch the warnings by explicitly ignoring the sizeof function.
>>
>> It just hides the warning leaving the real problem untouched. If you
>> really don't want to see those, I guess installing proper plugin for the
>> failing events will help you (in case you didn't).
>
> it wont' help, sizeof is special.. AFAIK we did not figure
> out a way to handle that so far
>
> but I think it was used only in one trace subsystem.. maybe we
> could replace it and forbid to use it in future ;-)
Yep, I know. But I meant that if we have a handler for the failing
event, it might print the event without even using the sizeof somehow.
;-)
Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists