From: sashiko-bot@kernel.org
To: "Sizhe Liu" <liusizhe5@huawei.com>
Cc: linux-perf-users@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH v2 5/8] perf hisi-ptt: Add parsing of supported message types
Date: Thu, 27 Aug 2026 14:12:55 +0000 [thread overview]
Message-ID: <20260827141255.EE5B01F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260827140442.2031128-6-liusizhe5@huawei.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Missing explicit inclusion of <stdbool.h> for musl compatibility.
--
commit db9f8e2182c24e7486861ffcf7818bd57505c649
Author: Sizhe Liu <liusizhe5@huawei.com>
perf hisi-ptt: Add parsing of supported message types
This commit parses PCIe TLP messages into types like MWr, Msg, Atom, IO, CFG,
and CPL based on the Header DW0 Format and Type fields. The parsed message
type is stored in the packet buffer to select correct field layouts for later
processing.
> diff --git a/tools/perf/util/hisi-ptt-decoder/hisi-ptt-pkt-decoder.c b/tools/perf/util/hisi-ptt-decoder/hisi-ptt-pkt-decoder.c
> index 00bd9309df68a..e63fe1534693c 100644
> --- a/tools/perf/util/hisi-ptt-decoder/hisi-ptt-pkt-decoder.c
> +++ b/tools/perf/util/hisi-ptt-decoder/hisi-ptt-pkt-decoder.c
> @@ -79,6 +79,66 @@ static const char * const hisi_ptt_4dw_pkt_field_name[] = {
> [HISI_PTT_4DW_HEAD3] = "Header DW3",
> };
>
> +/* TLP message parsers below according to PCIe r6.4 sec 2.2.1.1 & 2.2.1.2 */
> +static bool hisi_ptt_is_mwr_tlp(uint32_t format, uint32_t type)
[Severity: Low]
Does this missing explicit inclusion of <stdbool.h> break compilation under
musl libc?
The Perf subsystem guidelines require explicit inclusion of POSIX standard
headers for types like bool, because unlike glibc, musl strictly separates
declarations and does not implicitly pull them in.
> +{
> + return (format == 0x2 || format == 0x3) && (type == 0);
> +}
> +
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260827140442.2031128-1-liusizhe5@huawei.com?part=5
next prev parent reply other threads:[~2026-08-27 14:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-27 14:04 [PATCH v2 0/8] Enhance TLP packet decoder with field-level parsing and versioning Sizhe Liu
2026-08-27 14:04 ` [PATCH v2 1/8] perf hisi-ptt: Abstract trace data buf and offset Sizhe Liu
2026-08-27 14:14 ` sashiko-bot
2026-08-27 14:04 ` [PATCH v2 2/8] perf hisi-ptt: Complete the field names for 4DW and 8DW packets Sizhe Liu
2026-08-27 14:10 ` sashiko-bot
2026-08-27 14:04 ` [PATCH v2 3/8] perf hisi-ptt: Extract the raw data printing part Sizhe Liu
2026-08-27 14:09 ` sashiko-bot
2026-08-27 14:04 ` [PATCH v2 4/8] perf hisi-ptt: Merge 4DW and 8DW HEAD0 printing Sizhe Liu
2026-08-27 14:10 ` sashiko-bot
2026-08-27 14:04 ` [PATCH v2 6/8] perf hisi-ptt: Add field-level parsing for header DW2/DW3 Sizhe Liu
2026-08-27 14:10 ` sashiko-bot
[not found] ` <20260827140442.2031128-6-liusizhe5@huawei.com>
2026-08-27 14:12 ` sashiko-bot [this message]
[not found] ` <20260827140442.2031128-9-liusizhe5@huawei.com>
2026-08-27 14:13 ` [PATCH v2 8/8] perf hisi-ptt: Pass pattern version to decoder for compatibility sashiko-bot
[not found] ` <20260827140442.2031128-8-liusizhe5@huawei.com>
2026-08-27 14:13 ` [PATCH v2 7/8] hwtracing: hisi_ptt: Add pattern PMU config for trace format selection sashiko-bot
2026-09-01 1:31 ` Yushan Wang
2026-09-02 3:30 ` Sizhe Liu
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=20260827141255.EE5B01F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=liusizhe5@huawei.com \
--cc=sashiko-reviews@lists.linux.dev \
/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