From: Shiju Jose <shiju.jose@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: "mhiramat@kernel.org" <mhiramat@kernel.org>,
"mathieu.desnoyers@efficios.com" <mathieu.desnoyers@efficios.com>,
"linux-trace-kernel@vger.kernel.org"
<linux-trace-kernel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linuxarm <linuxarm@huawei.com>,
Jonathan Cameron <jonathan.cameron@huawei.com>,
tanxiaofei <tanxiaofei@huawei.com>,
"Zengtao (B)" <prime.zeng@hisilicon.com>
Subject: RE: [PATCH 1/1] tracing: Support reading trace event format file larger than PAGE_SIZE
Date: Wed, 8 Jan 2025 10:34:03 +0000 [thread overview]
Message-ID: <cef1ea5d332e4382b26d233c72b8995f@huawei.com> (raw)
In-Reply-To: <20250107181921.2ba79257@gandalf.local.home>
>-----Original Message-----
>From: Steven Rostedt <rostedt@goodmis.org>
>Sent: 07 January 2025 23:19
>To: Shiju Jose <shiju.jose@huawei.com>
>Cc: mhiramat@kernel.org; mathieu.desnoyers@efficios.com; linux-trace-
>kernel@vger.kernel.org; linux-kernel@vger.kernel.org; Linuxarm
><linuxarm@huawei.com>; Jonathan Cameron
><jonathan.cameron@huawei.com>; tanxiaofei <tanxiaofei@huawei.com>;
>Zengtao (B) <prime.zeng@hisilicon.com>
>Subject: Re: [PATCH 1/1] tracing: Support reading trace event format file larger
>than PAGE_SIZE
>
>On Tue, 7 Jan 2025 18:02:24 -0500
>Steven Rostedt <rostedt@goodmis.org> wrote:
>
>> diff --git a/src/event-parse.c b/src/event-parse.c index
>> 33ed7fb47fff..f2e50b0e8992 100644
>> --- a/src/event-parse.c
>> +++ b/src/event-parse.c
>> @@ -7841,7 +7841,7 @@ static enum tep_errno parse_format(struct
>tep_event **eventp,
>> ret = event_read_format(event);
>> if (ret < 0) {
>> ret = TEP_ERRNO__READ_FORMAT_FAILED;
>> - goto event_parse_failed;
>> + goto event_alloc_failed;
>> }
>>
>> /*
>>
>>
>> As it's OK if it returns that it failed to parse the print format, as
>> it can still read the event. But if it fails to read the fields, then
>> it is basically useless.
>
>And the event you posted would still succeed. And it should succeed actually. It
>just failed to parse the print format. There's a lot of events that do as the print
>format is pretty much full C code, and libtraceveent is not a full C parser. It can
>also call functions that it doesn't know about which means even if it were a full C
>parser it would still fail to parse.
>
>But it does flag the event as "TEP_EVENT_FL_FAILED", and should display
>"[FAILED_TO_PARSE]" when printing the generic output.
>
Ok.
>I still think failing to parse the fields is more of a critical error though. That
>shouldn't happen, and if it does, it should be corrected.
As reported previously, parsing fields succeed in the rasdaemon for CXL events, when format file is larger than
PAGE_SIZE, with the rasdaemon change for reading complete format file.
>
>-- Steve
Thanks,
Shiju
next prev parent reply other threads:[~2025-01-08 10:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 17:43 [PATCH 1/1] tracing: Support reading trace event format file larger than PAGE_SIZE shiju.jose
2025-01-06 17:22 ` Steven Rostedt
2025-01-06 18:15 ` Shiju Jose
2025-01-06 22:11 ` Steven Rostedt
2025-01-07 11:04 ` Shiju Jose
2025-01-07 23:02 ` Steven Rostedt
2025-01-07 23:19 ` Steven Rostedt
2025-01-08 10:34 ` Shiju Jose [this message]
2025-01-08 10:19 ` Shiju Jose
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=cef1ea5d332e4382b26d233c72b8995f@huawei.com \
--to=shiju.jose@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=prime.zeng@hisilicon.com \
--cc=rostedt@goodmis.org \
--cc=tanxiaofei@huawei.com \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).