From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, Eric Anholt <eric@anholt.net>
Subject: [PATCH 0/6] vc4 miscellaneous v3d fixes
Date: Tue, 26 Jul 2016 13:47:09 -0700 [thread overview]
Message-ID: <1469566035-22006-1-git-send-email-eric@anholt.net> (raw)
Here are a bunch of miscellaneous fixes for 3D I've come up with while
doing a bunch of piglit runs. One has a new IGT test sent out, and
I've got a test almost ready for large CLs.
Eric Anholt (6):
drm/vc4: Use drm_free_large() on handles to match its allocation.
drm/vc4: Use drm_malloc_ab to fix large rendering jobs.
drm/vc4: Fix handling of a pm_runtime_get_sync() success case.
drm/vc4: Free hang state before destroying BO cache.
drm/vc4: Fix overflow mem unreferencing when the binner runs dry.
drm/vc4: Fix oops when userspace hands in a bad BO.
drivers/gpu/drm/vc4/vc4_drv.c | 6 +++---
drivers/gpu/drm/vc4/vc4_drv.h | 9 +++++++++
drivers/gpu/drm/vc4/vc4_gem.c | 18 +++++++++---------
drivers/gpu/drm/vc4/vc4_irq.c | 4 +++-
4 files changed, 24 insertions(+), 13 deletions(-)
--
2.8.1
next reply other threads:[~2016-07-26 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 20:47 Eric Anholt [this message]
2016-07-26 20:47 ` [PATCH 1/6] drm/vc4: Use drm_free_large() on handles to match its allocation Eric Anholt
2016-07-26 20:47 ` [PATCH 2/6] drm/vc4: Use drm_malloc_ab to fix large rendering jobs Eric Anholt
2016-07-26 20:47 ` [PATCH 3/6] drm/vc4: Fix handling of a pm_runtime_get_sync() success case Eric Anholt
2016-07-26 20:47 ` [PATCH 4/6] drm/vc4: Free hang state before destroying BO cache Eric Anholt
2016-07-26 20:47 ` [PATCH 5/6] drm/vc4: Fix overflow mem unreferencing when the binner runs dry Eric Anholt
2016-07-26 21:10 ` Rob Clark
2016-07-26 23:11 ` Eric Anholt
2016-07-26 23:37 ` Rob Clark
2016-07-27 5:37 ` Eric Anholt
2016-07-27 11:18 ` Rob Clark
2016-07-26 20:47 ` [PATCH 6/6] drm/vc4: Fix oops when userspace hands in a bad BO Eric Anholt
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=1469566035-22006-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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