Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915/gem_mman: Add helper routine to check GTT version
Date: Sun, 17 Nov 2019 22:12:32 +0000	[thread overview]
Message-ID: <c0c88ecc576ec4d6ad19d02bfb17a343f85c7ea5.camel@intel.com> (raw)
In-Reply-To: <157400169496.24372.15824845542482878106@skylake-alporthouse-com>


[-- Attachment #1.1: Type: text/plain, Size: 482 bytes --]

On Sun, 2019-11-17 at 14:41 +0000, Chris Wilson wrote:
> Quoting Stuart Summers (2019-11-17 14:39:16)
> > Add a check to gem_pread and gem_pwrite to only allow GTT subtests
> > when the GTT version is at least 1.
> 
> No, it must also run on kernels before ioctl versioning. Why?

Hm.. yeah that makes sense. I'll have to come up with something else :)
Looking for a way to determine whether we can mmap to the GTT. I'll
rethink and repost.

Thanks,
Stuart

> -Chris

[-- Attachment #1.2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3270 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-11-17 22:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-17 14:39 [igt-dev] [PATCH i-g-t] lib/i915/gem_mman: Add helper routine to check GTT version Stuart Summers
2019-11-17 14:41 ` Chris Wilson
2019-11-17 22:12   ` Summers, Stuart [this message]
2019-11-18 10:24     ` Chris Wilson
2019-11-17 15:08 ` [igt-dev] ✗ Fi.CI.BAT: failure for " 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=c0c88ecc576ec4d6ad19d02bfb17a343f85c7ea5.camel@intel.com \
    --to=stuart.summers@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@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