From: Damien Lespiau <damien.lespiau@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org,
Tomasz Madajczak <tomasz.madajczak@intel.com>
Subject: Re: [PATCH] drm/i915: Revert "drm/i915: Reject the pin ioctl on gen6+"
Date: Fri, 19 Sep 2014 15:25:55 +0100 [thread overview]
Message-ID: <20140919142555.GA19670@strange.ger.corp.intel.com> (raw)
In-Reply-To: <20140707210455.GF17271@phenom.ffwll.local>
Hi Daniel,
On Mon, Jul 07, 2014 at 11:04:55PM +0200, Daniel Vetter wrote:
> On Thu, Jul 03, 2014 at 08:12:35AM +0100, Damien Lespiau wrote:
> > This reverts commit 02f6bcccf7c324115747aae2f0addd6af5d321cd.
> >
> > The OA buffer can contain global data (in particular, not linked to a
> > context or a single batch execution) about GPU events (eg. hw context
> > switches, rc6 transitions, frequency changes, ...) and needs to be
> > mapped to GGTT. The pin ioctl provided a way to do that.
> >
> > Admittedly, this change broke what seems to be a valid use case of
> > pinning a buffer in GGTT, even when PPGTT is used (which is the reason
> > invoked in the commit message).
>
> Global OA buffers should be handled by the kernel and exposed through
> perf, imo. I think I'll go lalala on this a bit longer ...
Do you think that we can unblock this now that we have somewhat of path
forward with Rob Bragg's work? I'm still uneasy with a precedent where
we break working applications and it takes a long time for us to revert
the offending change?
Thanks!
--
Damien
next prev parent reply other threads:[~2014-09-19 14:26 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 [this message]
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
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=20140919142555.GA19670@strange.ger.corp.intel.com \
--to=damien.lespiau@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tomasz.madajczak@intel.com \
/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