From: Ramon Fried <ramon.fried@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/5] common: iotrace: add timestamp to iotrace records
Date: Thu, 24 May 2018 22:36:02 +0300 [thread overview]
Message-ID: <20180524193604.28280-4-ramon.fried@gmail.com> (raw)
In-Reply-To: <20180524193604.28280-1-ramon.fried@gmail.com>
Add timestamp to each iotrace record to aid in debugging
of IO timing access bugs.
Signed-off-by: Ramon Fried <ramon.fried@gmail.com>
---
common/iotrace.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/common/iotrace.c b/common/iotrace.c
index f39885663a..3530688ab1 100644
--- a/common/iotrace.c
+++ b/common/iotrace.c
@@ -27,11 +27,13 @@ enum iotrace_flags {
* struct iotrace_record - Holds a single I/O trace record
*
* @flags: I/O access type
+ * @timestamp: Timestamp of access
* @addr: Address of access
* @value: Value written or read
*/
struct iotrace_record {
enum iotrace_flags flags;
+ u64 timestamp;
phys_addr_t addr;
iovalue_t value;
};
@@ -82,6 +84,7 @@ static void add_record(int flags, const void *ptr, ulong value)
sizeof(value));
}
+ rec->timestamp = get_ticks();
rec->flags = flags;
rec->addr = map_to_sysmem(ptr);
rec->value = value;
--
2.17.0
next prev parent reply other threads:[~2018-05-24 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-24 19:35 [U-Boot] [PATCH 0/5] Iotrace improvements Ramon Fried
2018-05-24 19:36 ` [U-Boot] [PATCH 1/5] cmd: iotrace: add set region command Ramon Fried
2018-05-24 19:36 ` [U-Boot] [PATCH 2/5] iotrace: add IO region limit Ramon Fried
2018-05-24 19:36 ` Ramon Fried [this message]
2018-05-24 19:36 ` [U-Boot] [PATCH 4/5] iotrace: move record definitons to header file Ramon Fried
2018-05-24 19:36 ` [U-Boot] [PATCH 5/5] cmd: iotrace: add dump trace command Ramon Fried
2018-05-26 2:07 ` Simon Glass
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=20180524193604.28280-4-ramon.fried@gmail.com \
--to=ramon.fried@gmail.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