public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH i-g-t] i915/gem_exec_limit: Limit to a maximum of 120s
Date: Mon, 14 Jan 2019 09:42:55 +0000	[thread overview]
Message-ID: <db676bc7-8dfe-2330-2bf9-021f33220a41@linux.intel.com> (raw)
In-Reply-To: <20190114091647.8700-1-chris@chris-wilson.co.uk>


On 14/01/2019 09:16, Chris Wilson wrote:
> Each individual pass is as effective at spotting an error using the
> Chinese whisper as any other, so the effectiveness of adding more passes
> rapidly diminishes. To keep the tests bounded within time, limit a
> subtest to a mere 150s!
> 
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108592
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>   tests/i915/gem_exec_whisper.c | 13 +++++++++----

I was wondering what gem_exec_limit was! :)

>   1 file changed, 9 insertions(+), 4 deletions(-)
> 
> diff --git a/tests/i915/gem_exec_whisper.c b/tests/i915/gem_exec_whisper.c
> index 81303f847..d2ee98399 100644
> --- a/tests/i915/gem_exec_whisper.c
> +++ b/tests/i915/gem_exec_whisper.c
> @@ -189,12 +189,12 @@ static void whisper(int fd, unsigned engine, unsigned flags)
>   	unsigned engines[16];
>   	unsigned nengine;
>   	uint32_t batch[16];
> -	int i, n, pass, loc;
>   	unsigned int relocations = 0;
>   	unsigned int reloc_migrations = 0;
>   	unsigned int reloc_interruptions = 0;
>   	unsigned int eb_migrations = 0;
>   	uint64_t old_offset;
> +	int i, n, loc;
>   	int debugfs;
>   
>   	if (flags & PRIORITY) {
> @@ -323,7 +323,9 @@ static void whisper(int fd, unsigned engine, unsigned flags)
>   		}
>   
>   		igt_while_interruptible(flags & INTERRUPTIBLE) {
> -			for (pass = 0; pass < 1024; pass++) {
> +			unsigned int pass = 0;
> +
> +			igt_until_timeout(150) {
>   				uint64_t offset;
>   
>   				if (!(flags & FORKED))
> @@ -384,10 +386,10 @@ static void whisper(int fd, unsigned engine, unsigned flags)
>   						handle[1] = batches[n].handle;
>   						batches[n-1].handle =
>   							gem_open(this_fd,
> -									gem_flink(fd, handle[0]));
> +								 gem_flink(fd, handle[0]));
>   						batches[n].handle =
>   							gem_open(this_fd,
> -									gem_flink(fd, handle[1]));
> +								 gem_flink(fd, handle[1]));
>   						if (flags & PRIORITY)
>   							ctx_set_random_priority(this_fd, 0);
>   					}
> @@ -462,6 +464,9 @@ static void whisper(int fd, unsigned engine, unsigned flags)
>   
>   				store = tmp[1];
>   				scratch = tmp[0];
> +
> +				if (++pass == 1024)
> +					break;
>   			}
>   		}
>   		igt_info("Number of migrations for execbuf: %d\n", eb_migrations);

Log number of passes while at it?

> 

Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>

Regards,

Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-01-14  9:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14  9:16 [igt-dev] [PATCH i-g-t] i915/gem_exec_limit: Limit to a maximum of 120s Chris Wilson
2019-01-14  9:42 ` Tvrtko Ursulin [this message]
2019-01-14  9:53   ` [igt-dev] [Intel-gfx] " Chris Wilson
2019-01-14  9:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-01-14 11:42 ` [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=db676bc7-8dfe-2330-2bf9-021f33220a41@linux.intel.com \
    --to=tvrtko.ursulin@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    /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