From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH] drm/i915: Disable full ppgtt by default
Date: Thu, 6 Mar 2014 10:01:12 -0800 [thread overview]
Message-ID: <20140306100112.37e6794c@jbarnes-desktop> (raw)
In-Reply-To: <1394104461-13382-1-git-send-email-daniel.vetter@ffwll.ch>
On Thu, 6 Mar 2014 12:14:21 +0100
Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> There are too many oustanding issues:
>
> - Fence handling in the current code is broken. There's a patch series
> from me, but it's blocked on and extended review (which includes
> writing the testcases).
>
> - IOMMU mapping handling is broken, we need to properly refcount it -
> currently it gets destroyed when the first vma is unbound, so way
> too early.
>
> - There's a pending reset issue on snb. Since Mika's reset work and
> full ppgtt have been pulled in in separate branches and ended up
> intermittingly breaking each another it's unclear who's the exact
> culprit here.
>
> - We still have persistent evidince of crazy recursion bugs through
> vma_unbind and ppgtt_relase, e.g.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=73383
>
> This issue (and a few others meanwhile resolved) have blocked our
> performance measuring/tuning group since 3 months.
>
> - Secure batch dispatching is broken. This is blocking Brad Volkin's
> command checker work since 3 months.
Do we have bugs and/or tasks filed for all these, or just the one? We
need to make sure people are signed up to fix/review them, or it'll end
up staying disabled forever, and then we'll be stuck without a command
checker and some advanced features coming up...
--
Jesse Barnes, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-03-06 18:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-06 11:14 [PATCH] drm/i915: Disable full ppgtt by default Daniel Vetter
2014-03-06 18:01 ` Jesse Barnes [this message]
2014-03-06 18:17 ` Ben Widawsky
2014-03-06 20:30 ` Daniel Vetter
2014-03-06 21:42 ` Daniel Vetter
2014-03-06 21:55 ` Ben Widawsky
2014-03-18 10:19 ` Daniel Vetter
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=20140306100112.37e6794c@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=ben@bwidawsk.net \
--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