Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Derek Morton <derek.j.morton@intel.com>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH i-g-t v3 1/6] ioctl_wrappers: make gem_has_ring non static
Date: Mon, 14 Mar 2016 12:29:48 +0000	[thread overview]
Message-ID: <56E6AEBC.5010708@intel.com> (raw)
In-Reply-To: <1457607814-18751-2-git-send-email-derek.j.morton@intel.com>



On 10/03/16 11:03, Derek Morton wrote:
> For tests that use multiple rings to test interactions it is
> useful to know if a ring exists without triggering the test to skip.
>
> Signed-off-by: Derek Morton <derek.j.morton@intel.com>
> ---
>   lib/ioctl_wrappers.c | 2 +-
>   lib/ioctl_wrappers.h | 1 +
>   2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/lib/ioctl_wrappers.c b/lib/ioctl_wrappers.c
> index 5d49729..f42e2c9 100644
> --- a/lib/ioctl_wrappers.c
> +++ b/lib/ioctl_wrappers.c
> @@ -1396,7 +1396,7 @@ void gem_require_caching(int fd)
>   	errno = 0;
>   }
>   
> -static int gem_has_ring(int fd, int ring)
> +int gem_has_ring(int fd, int ring)

If this becomes non-static it will need documentation, also to explain 
how it differs from gem_has_enable_ring.

Regards,
Daniele

>   {
>   	uint32_t bbe = MI_BATCH_BUFFER_END;
>   	struct drm_i915_gem_execbuffer2 execbuf;
> diff --git a/lib/ioctl_wrappers.h b/lib/ioctl_wrappers.h
> index f59eafb..e095c41 100644
> --- a/lib/ioctl_wrappers.h
> +++ b/lib/ioctl_wrappers.h
> @@ -150,6 +150,7 @@ uint64_t gem_global_aperture_size(int fd);
>   uint64_t gem_mappable_aperture_size(void);
>   bool gem_has_softpin(int fd);
>   
> +int gem_has_ring(int fd, int ring);
>   /* check functions which auto-skip tests by calling igt_skip() */
>   void gem_require_caching(int fd);
>   void gem_require_ring(int fd, int ring_id);

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

  reply	other threads:[~2016-03-14 12:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 11:03 [PATCH i-g-t v3 0/6] Scheduler tests Derek Morton
2016-03-10 11:03 ` [PATCH i-g-t v3 1/6] ioctl_wrappers: make gem_has_ring non static Derek Morton
2016-03-14 12:29   ` Daniele Ceraolo Spurio [this message]
2016-03-29 13:08     ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 2/6] lib/intel_batchbuffer: Add functions to be used in the scheduler test Derek Morton
2016-03-14 12:16   ` Daniele Ceraolo Spurio
2016-03-29 15:04     ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 3/6] tests/gem_scheduler: Add gem_scheduler test Derek Morton
2016-03-17  8:49   ` Daniele Ceraolo Spurio
2016-03-17 10:33     ` Daniele Ceraolo Spurio
2016-03-10 11:03 ` [PATCH i-g-t v3 4/6] igt/gem_ctx_param_basic: Updated to support scheduler priority interface Derek Morton
2016-03-10 11:03 ` [PATCH i-g-t v3 5/6] tests/gem_scheduler: Add subtests to test batch priority behaviour Derek Morton
2016-03-17  8:58   ` Daniele Ceraolo Spurio
2016-03-30  8:19     ` Morton, Derek J
2016-03-10 11:03 ` [PATCH i-g-t v3 6/6] gem_scheduler: Added subtests to test priority bumping Derek Morton

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=56E6AEBC.5010708@intel.com \
    --to=daniele.ceraolospurio@intel.com \
    --cc=derek.j.morton@intel.com \
    --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