From: Ashutosh Dixit <ashutosh.dixit@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [CI 0/1] drm/i915: Disable pread/pwrite ioctl's for IGT testing
Date: Mon, 15 Mar 2021 20:49:06 -0700 [thread overview]
Message-ID: <cover.1615865509.git.ashutosh.dixit@intel.com> (raw)
FOR CI ONLY. PLEASE DON'T REVIEW.
The upstream guidance at this time is to start phasing out
pread/pwrite ioctl's, the rationale being (a) the functionality can be
done entirely in userspace with a combination of mmap + memcpy, and
(b) no existing user mode clients actually use the pread/pwrite
interface.
The plan is to phase out these ioctls for _new_ Gen12+ platforms. However,
since this patch is actually for CI and the real changes which need to be
validated are in IGT, in this patch we are disabling pread/pwrite for
existing Gen11 and Gen12 platforms. This will be changed once IGT changes
are validated and finalized.
Test-with: 20210315225356.2865-1-ashutosh.dixit@intel.com
Ashutosh Dixit (1):
drm/i915: Disable pread/pwrite ioctl's for IGT testing
drivers/gpu/drm/i915/i915_gem.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
--
2.29.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-03-16 3:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 3:49 Ashutosh Dixit [this message]
2021-03-16 3:49 ` [Intel-gfx] [CI 1/1] drm/i915: Disable pread/pwrite ioctl's for IGT testing Ashutosh Dixit
2021-03-16 4:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Disable pread/pwrite ioctl's for IGT testing (rev4) Patchwork
2021-03-16 4:47 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2021-01-21 20:09 [Intel-gfx] [CI 0/1] drm/i915: Disable pread/pwrite ioctl's for IGT testing Ashutosh Dixit
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=cover.1615865509.git.ashutosh.dixit@intel.com \
--to=ashutosh.dixit@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 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.