From: John.C.Harrison@Intel.com
To: Intel-GFX@Lists.FreeDesktop.Org
Subject: [PATCH 0/4] Convert requests to use struct fence
Date: Fri, 26 Jun 2015 13:58:08 +0100 [thread overview]
Message-ID: <1435323492-28630-1-git-send-email-John.C.Harrison@Intel.com> (raw)
From: John Harrison <John.C.Harrison@Intel.com>
There is a construct in the linux kernel called 'struct fence' that is intended
to keep track of work that is executed on hardware. I.e. it solves the basic
problem that the drivers 'struct drm_i915_gem_request' is trying to address. The
request structure does quite a lot more than simply track the execution progress
so is very definitely still required. However, the basic completion status side
could be updated to use the ready made fence implementation and gain all the
advantages that provides.
This is work that was planned since the conversion of the driver from being
seqno value based to being request structure based. This patch series does that
work.
[Patches against drm-intel-nightly tree fetched 23/06/2015]
John Harrison (4):
drm/i915: Convert requests to use struct fence
drm/i915: Removed now redudant parameter to i915_gem_request_completed()
drm/i915: Interrupt driven fences
drm/i915: Updated request structure tracing
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 52 +++++----
drivers/gpu/drm/i915/i915_gem.c | 195 +++++++++++++++++++++++++++++---
drivers/gpu/drm/i915/i915_irq.c | 4 +-
drivers/gpu/drm/i915/i915_trace.h | 7 +-
drivers/gpu/drm/i915/intel_display.c | 2 +-
drivers/gpu/drm/i915/intel_lrc.c | 3 +
drivers/gpu/drm/i915/intel_pm.c | 4 +-
drivers/gpu/drm/i915/intel_ringbuffer.c | 3 +
drivers/gpu/drm/i915/intel_ringbuffer.h | 5 +
10 files changed, 232 insertions(+), 45 deletions(-)
--
1.9.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2015-06-26 12:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-26 12:58 John.C.Harrison [this message]
2015-06-26 12:58 ` [PATCH 1/4] drm/i915: Convert requests to use struct fence John.C.Harrison
2015-06-26 12:58 ` [PATCH 2/4] drm/i915: Removed now redudant parameter to i915_gem_request_completed() John.C.Harrison
2015-06-26 12:58 ` [PATCH 3/4] drm/i915: Interrupt driven fences John.C.Harrison
2015-06-26 13:34 ` Chris Wilson
2015-06-26 17:00 ` John Harrison
2015-06-26 17:19 ` Chris Wilson
2015-06-26 12:58 ` [PATCH 4/4] drm/i915: Updated request structure tracing John.C.Harrison
2015-06-28 15:07 ` shuang.he
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=1435323492-28630-1-git-send-email-John.C.Harrison@Intel.com \
--to=john.c.harrison@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.