From: Michal Simek <michal.simek@amd.com>
To: <u-boot@lists.denx.de>, <git@xilinx.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: [PATCH 0/3] trace: Fix flyrecord alignment issue
Date: Mon, 11 Sep 2023 14:32:26 +0200 [thread overview]
Message-ID: <cover.1694435541.git.michal.simek@amd.com> (raw)
Hi,
sandbox is getting bigger and bigger and I have reached the case that
adding some more functions ends up in CI loop failure. After some
investigation I found that flyrecord header have incorrect information
about data offset which is caused by incorrect alignment calculation.
That's why this series is fixing alignment calculation.
I have done it via 3 patches where the first two are just preparing code
for actual fixup.
Thanks,
Michal
Michal Simek (3):
trace: Use 64bit variable for start and len
trace: Move trace_clocks description above record offset calculation
trace: Fix alignment logic in flyrecord header
tools/proftool.c | 39 ++++++++++++++++++++++++++++++++++-----
1 file changed, 34 insertions(+), 5 deletions(-)
--
2.36.1
next reply other threads:[~2023-09-11 12:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 12:32 Michal Simek [this message]
2023-09-11 12:32 ` [PATCH 1/3] trace: Use 64bit variable for start and len Michal Simek
2023-09-12 19:26 ` Simon Glass
2023-09-14 14:54 ` Michal Simek
2023-09-11 12:32 ` [PATCH 2/3] trace: Move trace_clocks description above record offset calculation Michal Simek
2023-09-12 19:26 ` Simon Glass
2023-09-11 12:32 ` [PATCH 3/3] trace: Fix alignment logic in flyrecord header Michal Simek
2023-09-12 19:26 ` Simon Glass
2023-09-14 14:58 ` Michal Simek
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=cover.1694435541.git.michal.simek@amd.com \
--to=michal.simek@amd.com \
--cc=git@xilinx.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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