From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Tvrtko Ursulin <tursulin@ursulin.net>,
igt-dev@lists.freedesktop.org
Cc: Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 1/7] gem_wsim: Check sleep times
Date: Tue, 14 Aug 2018 16:21:08 +0100 [thread overview]
Message-ID: <934ae971-492f-033e-a011-2d28f10c55ef@linux.intel.com> (raw)
In-Reply-To: <153425935575.3371.7564394383875986620@skylake-alporthouse-com>
On 14/08/2018 16:09, Chris Wilson wrote:
> Quoting Tvrtko Ursulin (2018-08-14 16:05:13)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> Notice in more places if we are running behind.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>> ---
>> benchmarks/gem_wsim.c | 52 ++++++++++++++++++++++++++++++++++++++-----
>> 1 file changed, 46 insertions(+), 6 deletions(-)
>>
>> diff --git a/benchmarks/gem_wsim.c b/benchmarks/gem_wsim.c
>> index 80f180829241..ead91b0f009b 100644
>> --- a/benchmarks/gem_wsim.c
>> +++ b/benchmarks/gem_wsim.c
>> @@ -1718,6 +1718,21 @@ static bool sync_deps(struct workload *wrk, struct w_step *w)
>> return synced;
>> }
>>
>> +static unsigned int measured_usleep(unsigned int usec)
>> +{
>> + struct timespec ts = { };
>> + unsigned int slept;
>> +
>> + slept = igt_nsec_elapsed(&ts);
>> + igt_assert(slept == 0);
>> + do {
>> + usleep(usec - slept);
>> + slept = igt_nsec_elapsed(&ts) / 1000;
>> + } while (slept < usec);
>> +
>> + return igt_nsec_elapsed(&ts);
>> +}
>> +
>> static void *run_workload(void *data)
>> {
>> struct workload *wrk = (struct workload *)data;
>> @@ -1739,7 +1754,7 @@ static void *run_workload(void *data)
>> count++) {
>> unsigned int cur_seqno = wrk->sync_seqno;
>>
>> - clock_gettime(CLOCK_MONOTONIC, &wrk->repeat_start);
>> + igt_gettime(&wrk->repeat_start);
>
> Were you already linking against libigt?
> This code is not set up to hit an igt_assert()...
This code meaning gem_wsim? There's a lot of asserts in it already, and
when they trigger traceback looks fine. What do you think is missing?
Regards,
Tvrtko
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2018-08-14 15:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 15:05 [Intel-gfx] [PATCH i-g-t 0/7] gem_wsim fixes and new features Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 1/7] gem_wsim: Check sleep times Tvrtko Ursulin
2018-08-14 15:09 ` Chris Wilson
2018-08-14 15:21 ` Tvrtko Ursulin [this message]
2018-08-14 15:27 ` Chris Wilson
2018-08-14 18:27 ` Tvrtko Ursulin
2018-08-14 18:34 ` Chris Wilson
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 2/7] gem_wsim: Make workload commands case sensitive Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 3/7] gem_wsim: Context priority support Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 4/7] gem_wsim: Stop keeping batches mapped Tvrtko Ursulin
2018-08-14 15:13 ` Chris Wilson
2018-08-14 15:16 ` Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 5/7] gem_wsim: Make batches preemptable by default Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 6/7] gem_wsim: Per context preemption point control Tvrtko Ursulin
2018-08-14 15:05 ` [igt-dev] [PATCH i-g-t 7/7] gem_wsim: Fix BCS usage under VCS2 remap warning Tvrtko Ursulin
2018-08-14 16:27 ` [igt-dev] ✓ Fi.CI.BAT: success for gem_wsim fixes and new features Patchwork
2018-08-14 22:29 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=934ae971-492f-033e-a011-2d28f10c55ef@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
--cc=tvrtko.ursulin@intel.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 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).