linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Tzvetomir Stoyanov (VMware)" <tz.stoyanov@gmail.com>
To: rostedt@goodmis.org
Cc: linux-trace-devel@vger.kernel.org
Subject: [PATCH v2 0/4] Iterate over raw events in sorted order
Date: Wed,  7 Apr 2021 06:48:18 +0300	[thread overview]
Message-ID: <20210407034822.2373958-1-tz.stoyanov@gmail.com> (raw)

tracefs_iterate_raw_events(): read oldest events first.
Updated the unit tests and documentation according to the new logic of
the function.

v2 changes:
 - Conding style fixes.
 - Fixed typo in function name.

Tzvetomir Stoyanov (VMware) (4):
  libtracefs: Iterate over raw events in sorted order
  libtracefs: Unit test for iterate over raw events in sorted order
  libtracefs: Unit test for iterate over raw events in selected CPUs
  libtracefs: tracefs_iterate_raw_events() documentation update

 Documentation/libtracefs-events.txt |  14 +-
 src/tracefs-events.c                | 247 ++++++++++++++++++----------
 utest/tracefs-utest.c               |  31 +++-
 3 files changed, 190 insertions(+), 102 deletions(-)

-- 
2.30.2


             reply	other threads:[~2021-04-07  3:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-07  3:48 Tzvetomir Stoyanov (VMware) [this message]
2021-04-07  3:48 ` [PATCH v2 1/4] libtracefs: Iterate over raw events in sorted order Tzvetomir Stoyanov (VMware)
2021-04-07  3:48 ` [PATCH v2 2/4] libtracefs: Unit test for iterate " Tzvetomir Stoyanov (VMware)
2021-04-07  3:48 ` [PATCH v2 3/4] libtracefs: Unit test for iterate over raw events in selected CPUs Tzvetomir Stoyanov (VMware)
2021-04-07  3:48 ` [PATCH v2 4/4] libtracefs: tracefs_iterate_raw_events() documentation update Tzvetomir Stoyanov (VMware)

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=20210407034822.2373958-1-tz.stoyanov@gmail.com \
    --to=tz.stoyanov@gmail.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /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).