From: Damien Lespiau <damien.lespiau@intel.com>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Madajczak, Tomasz" <Tomasz.Madajczak@intel.com>
Subject: Re: [PATCH] drm/i915: Revert "drm/i915: Reject the pin ioctl on gen6+"
Date: Thu, 2 Oct 2014 22:47:19 +0100 [thread overview]
Message-ID: <20141002214719.GA29056@strange.ger.corp.intel.com> (raw)
In-Reply-To: <CAPM=9tzqWDkSB3-v6g2d8M5hC6En4M5=MmeBx4F=ymE5To1yag@mail.gmail.com>
Hi Dave,
On Fri, Oct 03, 2014 at 07:12:53AM +1000, Dave Airlie wrote:
> I thought we had an agreement that no features that were specific to
> the non-open source userspace drivers would be merged to the kernel,
> due to security and maintenance concerns, i.e. exactly this concern,
> we now have to maintain an interface that we can't regression test in
> public.
Actually, the pin ioctl() has been here for quite some time, since the
introduction of GEM, see:
http://lwn.net/Articles/283798/ section 8.2
That's why one side is arguing that it's not acceptable to break
user-space (open or closed , it doesn't matter at this point).
Daniel is saying that's a legacy artefact and it shouldn't be used
anymore, but breaking a user-space application is enough for me to at
least suggest a revert.
HTH,
--
Damien
prev parent reply other threads:[~2014-10-02 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 7:12 [PATCH] drm/i915: Revert "drm/i915: Reject the pin ioctl on gen6+" Damien Lespiau
2014-07-03 7:35 ` Chris Wilson
2014-07-07 21:04 ` Daniel Vetter
2014-07-07 21:18 ` Jesse Barnes
2014-09-19 14:25 ` Damien Lespiau
2014-09-19 15:34 ` Daniel Vetter
2014-10-02 10:40 ` Bloomfield, Jon
2014-10-02 21:12 ` Dave Airlie
2014-10-02 21:47 ` Damien Lespiau [this message]
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=20141002214719.GA29056@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=Tomasz.Madajczak@intel.com \
--cc=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--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