public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ramon Fried <ramon.fried@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/6] Iotrace improvements
Date: Mon, 28 May 2018 14:03:32 +0300	[thread overview]
Message-ID: <20180528110338.19783-1-ramon.fried@gmail.com> (raw)

These set of patches add few improvements to iotrace.
* Region limiting - allows setting an address and size where only
					io operations that falls into that address are
					logged.
* Timestamping - Timestamp every iotrace record with current timestamp
* dumping - iotrace dump command for dumping all records from buffer
			in a readable fashion.

In terms of backwards compatibility, the timestamp is not backward
compatible as it changes the iotrace record. so if one developed an
offline parsing tool it will be broken.
I though of adding #ifdef specific for that, but eventually I didn't.

v2:
	* fixed printf format
	* added a fix when the buffer is full
v3:
	* changed the "buffer full" scenario as
	recommended by Simon Glass.
	This fix  is dependand on a sperate patch that introduces
	WARN_ONCE definition in bug.h (https://patchwork.ozlabs.org/patch/921391/)

Ramon Fried (6):
  cmd: iotrace: add set region command
  iotrace: add IO region limit
  common: iotrace: add timestamp to iotrace records
  iotrace: move record definitons to header file
  cmd: iotrace: add dump trace command
  iotrace: fix behaviour when buffer is full

 cmd/iotrace.c     | 63 ++++++++++++++++++++++++++++++++++++++++++---
 common/iotrace.c  | 65 +++++++++++++++++++++++++++--------------------
 include/iotrace.h | 57 +++++++++++++++++++++++++++++++++++++++--
 3 files changed, 153 insertions(+), 32 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project

             reply	other threads:[~2018-05-28 11:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-28 11:03 Ramon Fried [this message]
2018-05-28 11:03 ` [U-Boot] [PATCH 1/6] cmd: iotrace: add set region command Ramon Fried
2018-05-28 11:03 ` [U-Boot] [PATCH 2/6] iotrace: add IO region limit Ramon Fried
2018-05-28 11:03 ` [U-Boot] [PATCH 3/6] common: iotrace: add timestamp to iotrace records Ramon Fried
2018-05-28 11:03 ` [U-Boot] [PATCH 4/6] iotrace: move record definitons to header file Ramon Fried
2018-05-28 11:03 ` [U-Boot] [PATCH v2 5/6] cmd: iotrace: add dump trace command Ramon Fried
2018-05-28 11:03 ` [U-Boot] [PATCH v2 6/6] iotrace: fix behaviour when buffer is full Ramon Fried
2018-05-30 19:18 ` [U-Boot] [PATCH v3 0/6] Iotrace improvements Simon Glass
2018-05-30 19:23   ` Ramon Fried

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=20180528110338.19783-1-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