From: Dave Gordon <david.s.gordon@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/2 v2] drm/i915: mark GEM objects as dirtied by CPU
Date: Wed, 9 Dec 2015 15:52:50 +0000 [thread overview]
Message-ID: <1449676372-6988-1-git-send-email-david.s.gordon@intel.com> (raw)
In-Reply-To: <1449593478-33649-1-git-send-email-david.s.gordon@intel.com>
This patchset covers various places where GEM objects are dirtied by
means of CPU writes.
The first patch covers cases where only one page is actually written;
here we can mark just the specific page in the pagecache dirty. This
applies to regular (shmfs-backed) objects only.
The second patch covers situations where a subrange that is not limited
to a single page is modified, or a whole object is filled with data via
CPU writes. In either case, the object is now dirty (i.e. backing store
is out-of-date w.r.t. current contents) and must be marked so or risk
losing its contents if evicted. For the whole-object cases, marking the
individual pages at the point of writing would not be a win; instead
put_pages() will propagate the object-dirty flag to each page iff the
object is ever evicted.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-12-09 15:53 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-08 16:51 [PATCH 0/3] drm/i915: mark GEM objects as dirtied by CPU Dave Gordon
2015-12-08 16:51 ` [PATCH 1/3] drm/i915: mark GEM objects as dirty when filled by the CPU Dave Gordon
2015-12-08 17:00 ` Chris Wilson
2015-12-08 18:06 ` Dave Gordon
2015-12-10 10:49 ` Daniel Vetter
2015-12-08 16:51 ` [PATCH 2/3] drm/i915: mark GEM objects as dirty when updated " Dave Gordon
2015-12-08 17:00 ` Chris Wilson
2015-12-08 18:43 ` Dave Gordon
2015-12-08 16:51 ` [PATCH 3/3] drm/i915: mark GEM objects as dirty when written " Dave Gordon
2015-12-08 17:03 ` Chris Wilson
2015-12-08 18:24 ` Dave Gordon
2015-12-10 13:10 ` Daniel Vetter
2015-12-09 15:52 ` Dave Gordon [this message]
2015-12-09 15:52 ` [PATCH 1/2 v2] drm/i915: mark GEM object pages dirty when mapped & " Dave Gordon
2015-12-10 13:29 ` Chris Wilson
2015-12-10 17:24 ` Dave Gordon
2015-12-10 21:04 ` Chris Wilson
2015-12-11 17:08 ` Daniel Vetter
2015-12-11 17:27 ` Chris Wilson
2015-12-09 15:52 ` [PATCH 2/2 v2] drm/i915: mark GEM objects dirty after overwriting their contents Dave Gordon
2015-12-10 13:22 ` Chris Wilson
2015-12-10 14:06 ` Daniel Vetter
2015-12-10 14:52 ` Chris Wilson
2015-12-11 17:09 ` Daniel Vetter
2015-12-10 16:19 ` Dave Gordon
2015-12-10 18:51 ` [PATCH 0/4 v3] drm/i915: mark GEM objects as dirtied by CPU Dave Gordon
2015-12-10 18:51 ` [PATCH 1/4 v3] drm/i915: mark GEM object pages dirty when mapped & written by the CPU Dave Gordon
2015-12-10 21:07 ` Chris Wilson
2015-12-10 18:51 ` [PATCH 2/4 v3] drm/i915: mark a newly-created GEM object dirty when filled with data Dave Gordon
2015-12-10 21:06 ` Chris Wilson
2015-12-11 17:21 ` Daniel Vetter
2015-12-10 18:51 ` [PATCH 3/4 v3] drm/i915: always mark the target of pwrite() as dirty Dave Gordon
2015-12-10 21:09 ` Chris Wilson
2015-12-10 18:51 ` [PATCH 4/4 v3] drm/i915: miscellaneous tiny tweaks to GEM object->dirty Dave Gordon
2015-12-10 21:16 ` Chris Wilson
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=1449676372-6988-1-git-send-email-david.s.gordon@intel.com \
--to=david.s.gordon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).