From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Jason Ekstrand <jason@jlekstrand.net>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 0/3] drm/i915: Drop legacy IOCTLs on new HW
Date: Mon, 15 Mar 2021 22:31:23 -0700 [thread overview]
Message-ID: <87eegfis0k.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <20210315143428.1471489-1-jason@jlekstrand.net>
On Mon, 15 Mar 2021 07:34:25 -0700, Jason Ekstrand wrote:
>
> These three patches exist to clean up some of our IOCTL mess in i915.
> We've got more clean-up we should do eventually, but these are some of the
> easiest to drop and most egregious cases.
>
> Test-with: 20210121083742.46592-1-ashutosh.dixit@intel.com
Hi Jason,
Sorry the above IGT build is too old and has been discarded so no tests
were running on actual HW as is mentioned here:
https://intel-gfx-ci.01.org/test-with.html
I resubmitted the IGT patch today so we have a newer IGT build and have
just resubmitted this series with that IGT build. There are no other
changes with the actual patches themselves.
Thanks.
--
Ashutosh
>
> Ashutosh Dixit (1):
> drm/i915: Disable pread/pwrite ioctl's for future platforms (v3)
>
> Jason Ekstrand (2):
> drm/i915/gem: Drop legacy execbuffer support (v2)
> drm/i915/gem: Drop relocation support on all new hardware (v5)
>
> .../gpu/drm/i915/gem/i915_gem_execbuffer.c | 113 ++----------------
> drivers/gpu/drm/i915/gem/i915_gem_ioctls.h | 2 -
> drivers/gpu/drm/i915/i915_drv.c | 2 +-
> drivers/gpu/drm/i915/i915_gem.c | 14 +++
> include/uapi/drm/i915_drm.h | 1 +
> 5 files changed, 26 insertions(+), 106 deletions(-)
>
> --
> 2.29.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-03-16 5:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 14:34 [Intel-gfx] [PATCH 0/3] drm/i915: Drop legacy IOCTLs on new HW Jason Ekstrand
2021-03-15 14:34 ` [Intel-gfx] [PATCH 1/3] drm/i915/gem: Drop legacy execbuffer support (v2) Jason Ekstrand
2021-03-15 14:34 ` [Intel-gfx] [PATCH 2/3] drm/i915/gem: Drop relocation support on all new hardware (v5) Jason Ekstrand
2021-03-17 14:39 ` [Intel-gfx] [PATCH] drm/i915/gem: Drop relocation support on all new hardware (v6) Jason Ekstrand
2021-03-17 14:41 ` Jason Ekstrand
2021-03-17 15:06 ` Zbigniew Kempczyński
2021-03-15 14:34 ` [Intel-gfx] [PATCH 3/3] drm/i915: Disable pread/pwrite ioctl's for future platforms (v3) Jason Ekstrand
2021-03-15 15:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Drop legacy IOCTLs on new HW Patchwork
2021-03-15 15:46 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-03-16 5:31 ` Dixit, Ashutosh [this message]
2021-03-17 23:40 ` [Intel-gfx] [PATCH 0/5] drm/i915: Clean up some of the i915 uAPI (v6) Jason Ekstrand
2021-03-17 23:40 ` [Intel-gfx] [PATCH 1/5] drm/i915/gem: Drop legacy execbuffer support (v2) Jason Ekstrand
2021-03-17 23:40 ` [Intel-gfx] [PATCH 2/5] drm/i915/gem: Drop relocation support on all new hardware (v6) Jason Ekstrand
2021-03-17 23:40 ` [Intel-gfx] [PATCH 3/5] drm/i915: Disable pread/pwrite ioctl's for future platforms (v3) Jason Ekstrand
2021-03-18 13:27 ` Daniel Vetter
2021-03-17 23:40 ` [Intel-gfx] [PATCH 4/5] drm/i915: Drop the CONTEXT_CLONE API Jason Ekstrand
2021-03-18 10:19 ` Tvrtko Ursulin
2021-03-17 23:40 ` [Intel-gfx] [PATCH 5/5] drm/i915: Drop I915_CONTEXT_PARAM_RINGSIZE Jason Ekstrand
2021-03-22 7:30 ` [Intel-gfx] [drm/i915] 3ef784da89: drm:add_taint_for_CI[i915]] kernel test robot
-- strict thread matches above, loose matches on Subject: below --
2021-03-16 5:29 [Intel-gfx] [PATCH 0/3] drm/i915: Drop legacy IOCTLs on new HW 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=87eegfis0k.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jason@jlekstrand.net \
/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