public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: David Weinehall <david.weinehall@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t 0/3] Unify slow/combinatorial test handling
Date: Mon, 26 Oct 2015 15:55:07 +0200	[thread overview]
Message-ID: <20151026135507.GA2504@boom> (raw)
In-Reply-To: <20151023124757.GR16848@phenom.ffwll.local>

On Fri, Oct 23, 2015 at 02:47:57PM +0200, Daniel Vetter wrote:
> On Fri, Oct 23, 2015 at 12:58:45PM +0100, Chris Wilson wrote:
> > On Fri, Oct 23, 2015 at 02:42:33PM +0300, David Weinehall wrote:
> > > Until now we've had no unified way to handle slow/combinatorial tests.
> > > Most of the time we don't want to run slow/combinatorial tests, so this
> > > should remain the default, but when we do want to run such tests,
> > > it has been handled differently in different tests.
> > > 
> > > This patch adds a --with-slow-combinatorial command line option to
> > > igt_core, changes gem_concurrent_blit and kms_frontbuffer_tracking
> > > to use this instead of their own methods, and removes gem_concurrent_all
> > > in the process, since it's now unnecessary.
> > 
> > I'm not going to remember the --with-slow-combinatorial option. How
> > about just --all, or --slow?
> 
> Yeah, --all as a shorthand sounds good to me.

OK, will rename it to '--all'.


Kind regards, David
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-10-26 13:55 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 11:42 [PATCH i-g-t 0/3] Unify slow/combinatorial test handling David Weinehall
2015-10-23 11:42 ` [PATCH i-g-t 1/3] Rename gem_concurren_all over gem_concurrent_blit David Weinehall
2015-10-23 14:32   ` Thomas Wood
2015-10-26 15:03     ` David Weinehall
2015-10-23 11:42 ` [PATCH i-g-t 2/3] Unify handling of slow/combinatorial tests David Weinehall
2015-10-23 11:56   ` Chris Wilson
2015-10-23 13:50   ` Paulo Zanoni
2015-10-26 14:59     ` David Weinehall
2015-10-26 16:44       ` Paulo Zanoni
2015-10-26 17:30         ` David Weinehall
2015-10-26 17:59           ` Paulo Zanoni
2015-10-27  6:47             ` David Weinehall
2015-11-17 15:33               ` Daniel Vetter
2015-11-17 15:34             ` Daniel Vetter
2015-11-17 15:49               ` Paulo Zanoni
2015-11-18 10:19                 ` David Weinehall
2015-10-23 14:55   ` Thomas Wood
2015-10-26 15:28     ` David Weinehall
2015-10-26 16:28       ` Thomas Wood
2015-10-26 17:34         ` David Weinehall
2015-10-26 18:15     ` Paulo Zanoni
2015-10-23 11:42 ` [PATCH i-g-t 3/3] Remove gem_concurrent_all, since it is now superfluous David Weinehall
2015-10-23 11:58 ` [PATCH i-g-t 0/3] Unify slow/combinatorial test handling Chris Wilson
2015-10-23 12:47   ` Daniel Vetter
2015-10-26 13:55     ` David Weinehall [this message]
2015-10-28 11:29 ` [PATCH i-g-t 0/3 v2] " David Weinehall
2015-10-28 11:29   ` [PATCH i-g-t 1/3] Copy gem_concurrent_all to gem_concurrent_blit David Weinehall
2015-10-28 11:29   ` [PATCH i-g-t 2/3] Unify handling of slow/combinatorial tests David Weinehall
2015-10-28 16:12     ` Paulo Zanoni
2015-10-30  7:56       ` David Weinehall
2015-10-30 11:55         ` Paulo Zanoni
2015-10-30 11:59           ` Chris Wilson
2015-10-28 17:14     ` Thomas Wood
2015-10-30  7:44       ` David Weinehall
2015-10-28 11:29   ` [PATCH i-g-t 3/3] Remove superfluous gem_concurrent_all.c David Weinehall
2015-10-30 13:18 ` [PATCH i-g-t 0/3 v3] Unify slow/combinatorial test handling David Weinehall
2015-10-30 13:18   ` [PATCH i-g-t 1/3 v3] Copy gem_concurrent_all to gem_concurrent_blit David Weinehall
2015-10-30 13:18   ` [PATCH i-g-t 2/3 v3] Unify handling of slow/combinatorial tests David Weinehall
2015-10-30 13:52     ` Chris Wilson
2015-11-12 11:00       ` David Weinehall
2015-10-30 13:18   ` [PATCH i-g-t 3/3 v3] Remove superfluous gem_concurrent_all.c David Weinehall

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=20151026135507.GA2504@boom \
    --to=david.weinehall@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --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