All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH 1/2] drm/i915: Simplify flush_cpu_write_domain
Date: Wed, 21 Jan 2015 15:53:50 +0100	[thread overview]
Message-ID: <20150121145350.GL10113@phenom.ffwll.local> (raw)
In-Reply-To: <20150121142120.GM19354@intel.com>

On Wed, Jan 21, 2015 at 04:21:20PM +0200, Ville Syrjälä wrote:
> On Wed, Jan 21, 2015 at 03:13:58PM +0100, Daniel Vetter wrote:
> > On Wed, Jan 21, 2015 at 3:08 PM, Ville Syrjälä
> > <ville.syrjala@linux.intel.com> wrote:
> > >> @@ -3735,7 +3733,7 @@ i915_gem_object_set_to_gtt_domain(struct drm_i915_gem_object *obj, bool write)
> > >>       if (ret)
> > >>               return ret;
> > >>
> > >> -     i915_gem_object_flush_cpu_write_domain(obj, false);
> > >> +     i915_gem_object_flush_cpu_write_domain(obj);
> > >
> > > This is the only place where there's a slight change in behaviour.
> > > Previosuly we would not clflush here when pin_display==true, but from
> > > now on we will. I had a patch to do only this change (part of some FBC
> > > series), but IIRC you argued it could hide bugs. I guess you've
> > > now changed you mind ;)
> > 
> > Hm, I don't remember that I've shot down a patch to change this and I
> > can't come up with any reason any more why. But you're right that the
> > commit message is a bit too silent about the behavioral change here.
> > Lazy me will try harder and augment it when merging.
> 
> http://lists.freedesktop.org/archives/intel-gfx/2013-November/036421.html

Well I didn't want the abi change really. But as a cleanup it seems
acceptable ;-)

Anyway added a bit of blurb and merged the patch, thanks for the feedback.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2015-01-21 14:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-21 13:53 [PATCH 1/2] drm/i915: Simplify flush_cpu_write_domain Daniel Vetter
2015-01-21 13:53 ` [PATCH 2/2] drm/i915: Remove open-coded callers of flush_cpu_write_domain Daniel Vetter
2015-01-21 14:08   ` Chris Wilson
2015-01-21 14:12   ` Ville Syrjälä
2015-01-21 14:55     ` Daniel Vetter
2015-01-21 15:02       ` Ville Syrjälä
2015-01-21 14:03 ` [PATCH 1/2] drm/i915: Simplify flush_cpu_write_domain Chris Wilson
2015-01-21 14:08 ` Ville Syrjälä
2015-01-21 14:13   ` Daniel Vetter
2015-01-21 14:21     ` Ville Syrjälä
2015-01-21 14:53       ` Daniel Vetter [this message]

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=20150121145350.GL10113@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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 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.