From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH V2 1/2] ltp: Add the ability to specify the latency constraint
Date: Thu, 17 Aug 2017 15:50:30 +0200 [thread overview]
Message-ID: <20170817135029.GA31322@rei> (raw)
In-Reply-To: <dafa7cdd-a9c6-1b1f-cbd8-b35d271d8d9f@linaro.org>
Hi!
> >> Yes, that make sense.
> >>
> >> Do you want keep the latency option for future use?
> >
> > I tend not to add anything just in case that we may need it later in
> > order to keep the test library as small as possible, it's complex enough
> > even as it is. Moreover we can always add it easily when we find a test
> > that requires it.
>
> Setting the latency to zero in tst_timer_start(), if the opening of the
> /dev/cpu_dma_latency file fails, we continue but issue a warning with
>
> tst_resm(TWARN,
> "Failed to open '/dev/cpu_dma_latency': %s',
> strerror(errno));
>
> is ok ?
Issuing TWARN marks the test as a failure, you should go for TINFO if
you want just inform the user about non-fatal problem.
Also are you sure that tst_timer_start() is the right place to open the
file? That function is called ~1000 times in each timer test hence this
would add quite a bit of overhead. Why don't we just put it into the
timer_setup() in the lib/tst_timer_test.c that is called once at the
start of the test?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-08-17 13:50 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 8:01 [LTP] [PATCH 1/2] ltp: Add the ability to specify the latency constraint Daniel Lezcano
2017-08-10 8:01 ` [LTP] [PATCH 2/2] syscalls/pselect: Add a zero " Daniel Lezcano
2017-08-10 11:50 ` Jiri Jaburek
2017-08-10 12:00 ` Daniel Lezcano
2017-08-11 11:26 ` Jan Stancek
2017-08-11 11:25 ` [LTP] [PATCH 1/2] ltp: Add the ability to specify the " Jan Stancek
2017-08-11 12:54 ` [LTP] [PATCH V2 " Daniel Lezcano
2017-08-11 12:54 ` [LTP] [PATCH V2 2/2] syscalls/pselect: Add a zero " Daniel Lezcano
2017-08-11 14:09 ` [LTP] [PATCH V2 1/2] ltp: Add the ability to specify the " Cyril Hrubis
2017-08-11 14:52 ` Daniel Lezcano
2017-08-11 15:28 ` Cyril Hrubis
2017-08-14 12:56 ` Daniel Lezcano
2017-08-14 13:33 ` Cyril Hrubis
2017-08-14 14:19 ` Daniel Lezcano
2017-08-14 14:36 ` Cyril Hrubis
2017-08-14 15:43 ` Daniel Lezcano
2017-08-15 11:06 ` Cyril Hrubis
2017-08-15 20:15 ` Daniel Lezcano
2017-08-17 13:50 ` Cyril Hrubis [this message]
2017-08-17 14:02 ` Daniel Lezcano
2017-08-17 15:00 ` [LTP] [PATCH V3] ltp: Add a zero latency constraint for the timer tests library Daniel Lezcano
2017-08-18 12:25 ` Cyril Hrubis
2017-12-12 14:48 ` Jan Stancek
2017-12-12 14:56 ` Daniel Lezcano
2017-12-12 15:04 ` Jan Stancek
2017-12-12 15:21 ` Daniel Lezcano
2017-12-13 17:00 ` Daniel Lezcano
2017-12-13 20:42 ` Jan Stancek
2018-02-01 22:52 ` Jan Stancek
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=20170817135029.GA31322@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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