public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH igt] igt/gem_exec_scheduler: HAS_SCHEDULER no longer means HAS_PREEMPTION
Date: Tue, 26 Sep 2017 15:14:39 +0300	[thread overview]
Message-ID: <1506428079.5228.10.camel@linux.intel.com> (raw)
In-Reply-To: <20170926093240.3786-1-chris@chris-wilson.co.uk>

On Tue, 2017-09-26 at 10:32 +0100, Chris Wilson wrote:
> Michal wants to limit machines that can do preemption, which means that
> we no longer can assume that if we have a scheduler for execbuf, that
> implies we have preemption.
> 
> v2: Try a capability mask instead
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
>  tests/gem_exec_schedule.c | 45 ++++++++++++++++++++++++++++-----------------
>  1 file changed, 28 insertions(+), 17 deletions(-)
> 
> diff --git a/tests/gem_exec_schedule.c b/tests/gem_exec_schedule.c
> index 0b1925f1..85c69703 100644
> --- a/tests/gem_exec_schedule.c
> +++ b/tests/gem_exec_schedule.c
> @@ -33,6 +33,8 @@
>  #include "igt_sysfs.h"
>  
>  #define LOCAL_PARAM_HAS_SCHEDULER 41
> +#define   HAS_SCHEDULER (1u << 0)
> +#define   HAS_PREEMPTION (1u << 2)

How about some BIT()? I think wehave it in IGT, at least I wrote
patches for it.

Looks good to me, can you reference the latest Mesa patches in here and
the kernel counterpart (reference the kernel counterpart here too).

Regards, Joonas
-- 
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2017-09-26 12:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25 20:48 [PATCH igt] igt/gem_exec_scheduler: HAS_SCHEDULER no longer means HAS_PREEMPTION Chris Wilson
2017-09-25 20:56 ` Chris Wilson
2017-09-25 21:25 ` ✓ Fi.CI.BAT: success for " Patchwork
2017-09-26  3:22 ` ✓ Fi.CI.IGT: " Patchwork
2017-09-26  9:32 ` [PATCH igt] " Chris Wilson
2017-09-26  9:41   ` Chris Wilson
2017-09-26 12:14   ` Joonas Lahtinen [this message]
2017-09-26 12:21     ` Chris Wilson
2017-09-27 12:24     ` Chris Wilson
2017-09-26 18:32 ` ✓ Fi.CI.BAT: success for igt/gem_exec_scheduler: HAS_SCHEDULER no longer means HAS_PREEMPTION (rev2) Patchwork
2017-09-27  3:36 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-27 18:47 ` [PATCH igt v3] igt/gem_exec_scheduler: HAS_SCHEDULER no longer means HAS_PREEMPTION Chris Wilson
2017-09-28 14:33   ` Joonas Lahtinen
2017-09-27 19:38 ` ✓ Fi.CI.BAT: success for igt/gem_exec_scheduler: HAS_SCHEDULER no longer means HAS_PREEMPTION (rev3) Patchwork
2017-09-28  1:16 ` ✗ Fi.CI.IGT: warning " Patchwork
2017-09-28 16:01 ` ✓ Fi.CI.IGT: success " 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=1506428079.5228.10.camel@linux.intel.com \
    --to=joonas.lahtinen@linux.intel.com \
    --cc=chris@chris-wilson.co.uk \
    --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