linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Punit Agrawal <punitagrawal@gmail.com>
To: jkacur@redhat.com
Cc: Punit Agrawal <punitagrawal@gmail.com>,
	linux-rt-users@vger.kernel.org, punit1.agrawal@toshiba.co.jp
Subject: [PATCH v2 0/3] rteval: Fix issues with cyclictest.py module
Date: Fri, 17 Sep 2021 17:53:40 +0900	[thread overview]
Message-ID: <20210917085343.2775300-1-punitagrawal@gmail.com> (raw)

Hi,

Here's an updated version of the cyclictest fixes previously posted at
[0]. The changes in this version are to address feedback received on
the previous version.

v1 -> v2:
* Patch 1: Add an option (default off) to save cyclictest output
* Patch 3: Sort cpus returned by online_cpus() in cyclictest.py module

All feedback welcome.

Thanks,
Punit

[0] https://lore.kernel.org/all/20210902092452.726905-1-punitagrawal@gmail.com/

Punit Agrawal (3):
  rteval: cyclictest.py Enable logging cyclictest output
  rteval: cyclictest.py Parse max latencies from cyclictest output
  rteval: cyclictest.py: Sort the list of cpus

 rteval/modules/measurement/cyclictest.py | 44 ++++++++++++++++++++----
 1 file changed, 37 insertions(+), 7 deletions(-)

-- 
2.32.0


             reply	other threads:[~2021-09-17  8:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  8:53 Punit Agrawal [this message]
2021-09-17  8:53 ` [PATCH v2 1/3] rteval: cyclictest.py Enable logging cyclictest output Punit Agrawal
2021-11-09  6:59   ` Punit Agrawal
2021-11-09  7:00     ` Punit Agrawal
2021-09-17  8:53 ` [PATCH v2 2/3] rteval: cyclictest.py Parse max latencies from " Punit Agrawal
2021-09-17  8:53 ` [PATCH v2 3/3] rteval: cyclictest.py: Sort the list of cpus Punit Agrawal
2021-09-28  1:36 ` [PATCH v2 0/3] rteval: Fix issues with cyclictest.py module Punit Agrawal
2021-09-28  1:47   ` John Kacur

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=20210917085343.2775300-1-punitagrawal@gmail.com \
    --to=punitagrawal@gmail.com \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=punit1.agrawal@toshiba.co.jp \
    /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).