From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC] [PATCH] syscalls: Add timer measurement library
Date: Wed, 31 May 2017 10:30:45 +0200 [thread overview]
Message-ID: <20170531083045.GA2276@rei.lan> (raw)
In-Reply-To: <502320923.23716336.1496150233908.JavaMail.zimbra@redhat.com>
Hi!
> > Hmm, we can also fill in the standard tst_test structure in the test
> > then "override" some of the fields in the timer test library.
> >
> > I.e. test defines tst_test structure and the sampling function, timer
> > library main() stores and replaces setup & cleanup, sets the test
> > function then calls the tst_run_tcases() function. Does that sound
> > better?
>
> Yes. This would mean we extend tst_test struct and add sampling function.
> As long as rest of fields continue to work (with some exceptions [1]),
> it sounds good.
We can setup the test/sample functions as an union. As we can then
distinguish between them based on .tcnt being non-zero in a case of
standard test and expect sampling function to be set in a case of the
timer test. However this makes the whole interface less type safe and
also much harder to extend. I was thinking of adding support for NULL
terminated array of test funcitons as well since we have some testcases
that use the test() function as dispatcher with a long switch()
statement...
So maybe we should just add a few more function pointers there.
> I see you still want to keep timer library main(), but I'm not sure
> how you are going to select it instead of tst_test main.
Only the tst_timer_test.h should be included in the timer testcases
which includes tst_test.h after defining TST_NO_DEFAULT_MAIN, then we
can define timer specific main that saves cleanup/setup and replaces
these with the timer test cleanup/setup that calls the test specifc
cleanup/setup functions. The timer library main also has to set up the
test function and test options in the tst_test structure since I want to
avoid setting these in each of the testcases to avoid copy & paste
errors.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2017-05-31 8:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-26 12:33 [LTP] [RFC] [PATCH] syscalls: Add timer measurement library Cyril Hrubis
2017-05-29 15:53 ` Jan Stancek
2017-05-30 12:15 ` Cyril Hrubis
2017-05-30 13:17 ` Jan Stancek
2017-05-31 8:30 ` Cyril Hrubis [this message]
2017-05-31 8:42 ` Cyril Hrubis
2017-05-31 10:51 ` Jan Stancek
2017-06-01 8:01 ` Cyril Hrubis
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=20170531083045.GA2276@rei.lan \
--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 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.