From: Daniel Wagner <wagi@monom.org>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
Daniel Wagner <dwagner@suse.de>,
linux-rt-users@vger.kernel.org
Subject: Re: [rt-tests 0/4] Streamlining code base?
Date: Mon, 7 Sep 2020 10:13:13 +0200 [thread overview]
Message-ID: <20200907081313.vyw2ykaio6abfxfx@beryllium.lan> (raw)
In-Reply-To: <alpine.LFD.2.23.451.2009041112370.4562@fionn>
On Fri, Sep 04, 2020 at 11:40:06AM -0400, John Kacur wrote:
> I'm not saying this is the only legitimate approach, but I would like to
> keep the individual tools lightweight in rt-tests, so that you could run
> them individually in the embedded space as well as on large machines.
Sure, though I still think it would make sense to keep it flexible and
have a compile switch if needed. I'd like to avoid additional steps
between the measurement and interpretation. Any time we want to
add/change a thing, we need to touch more places.
Furthermore, if you look at my implementation for the JSON output of
jitterdebugger is really small:
https://github.com/igaw/jitterdebugger/blob/master/jitterdebugger.c#L158
Adding a XML version for this should be in the same size.
If you insist on a single format (XML) that's also okay for me. Python
ships all the necessary libraries these days. Though the JSON format is
simpler to transform into native data types such as dictionaries and
lists, IMO.
Anyway, I don't have any strong feeling and have no real problem with
one format and a transform script.
> So one way to start would be to make sure that the other tools in the
> rt-tests suite are capable of generating a similar kind of output, that
> could then be processed by other tools.
Yes, I'd like to get consistent output from all tools.
Though I think we should start from the beginning and getting all
command line arguments parser, help texts and man pages consistent.
next prev parent reply other threads:[~2020-09-07 8:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 8:27 [rt-tests 0/4] Streamlining code base? Daniel Wagner
2020-09-02 8:27 ` [rt-tests 1/4] cyclicdeadline: Streamline usage output and man page Daniel Wagner
2020-09-02 8:27 ` [rt-tests 2/4] deadline_test: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 3/4] oslat: " Daniel Wagner
2020-09-02 8:27 ` [rt-tests 4/4] oslat: Use string parser utilies Daniel Wagner
2020-09-04 1:39 ` [rt-tests 0/4] Streamlining code base? Clark Williams
2020-09-04 6:31 ` Daniel Wagner
2020-09-04 15:40 ` John Kacur
2020-09-07 8:13 ` Daniel Wagner [this message]
2020-09-08 15:23 ` 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=20200907081313.vyw2ykaio6abfxfx@beryllium.lan \
--to=wagi@monom.org \
--cc=dwagner@suse.de \
--cc=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.