All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC i-g-t] tests/drv_hangman: test for acthd increasing through invalid VM space
Date: Tue, 23 Feb 2016 16:37:12 +0000	[thread overview]
Message-ID: <56CC8AB8.50509@intel.com> (raw)
In-Reply-To: <20160218211004.GB28380@nuc-i3427.alporthouse.com>



On 18/02/16 21:10, Chris Wilson wrote:
> On Thu, Feb 18, 2016 at 05:34:50PM +0000, daniele.ceraolospurio@intel.com wrote:
>> +static void ppgtt_walking(void)
>> +{
>> +	memset(&execbuf, 0, sizeof(execbuf));
>> +	execbuf.buffers_ptr = (uintptr_t)&gem_exec;
>> +	execbuf.buffer_count = 1;
>> +	execbuf.batch_len = 8;
>> +
>> +	gem_execbuf(fd, &execbuf);
>> +
>> +	while (gem_bo_busy(fd, handle) && timeout > 0) {
>> +		igt_debug("decreasing timeout to %u\n", --timeout);
>> +		sleep(1);
>> +	}
> See gem_wait()
> -Chris

I couldn't find any gem_wait() function or any other wrapper for the 
i915_gem_wait ioctl in ioctl_wrappers.c (except for gem_sync). There is 
a gem_bo_wait_timeout wrapper in gem_wait.c that could probably be moved 
to ioctl_wrappers, or I could just add the ioctl call here. What option 
would work better for you?

Thanks,
Daniele

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

  reply	other threads:[~2016-02-23 16:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18 17:34 [RFC i-g-t] tests/drv_hangman: test for acthd increasing through invalid VM space daniele.ceraolospurio
2016-02-18 21:10 ` Chris Wilson
2016-02-23 16:37   ` Daniele Ceraolo Spurio [this message]
2016-02-23 18:05     ` Chris Wilson

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=56CC8AB8.50509@intel.com \
    --to=daniele.ceraolospurio@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.