public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: "Gupta, Sourab" <sourab.gupta@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Rename GFX_TLB_INVALIDATE_ALWAYS
Date: Sat, 22 Mar 2014 12:23:56 +0100	[thread overview]
Message-ID: <20140322112356.GD26519@phenom.ffwll.local> (raw)
In-Reply-To: <1395458987.19358.53.camel@sourabgu-desktop>

On Sat, Mar 22, 2014 at 03:29:11AM +0000, Gupta, Sourab wrote:
> On Fri, 2014-03-21 at 17:18 +0000, Chris Wilson wrote:
> > The documentation calls this GFX_MODE bit "Flush TLB invalidate Mode".
> > However, that is not a good name for an enable bit as it doesn't make it
> > clear what is enabled. An even worse name is GFX_TLB_INVALIDATE_ALWAYS
> > as enabling that bit actually prevents the TLB from being invalidated at
> > every flush. This leads to great confusion when reading code and
> > proposed patches. To get around this try to bake in what is enabled by
> > setting the bit and call it GFX_TLB_INVALIDATE_EXPLICIT.
> > 
> 
> This looks fine. It clears the confusion around TLB INVALIDATE Bit.
> We'll be developing our patch on top of this and sending the full series
> of WA patches for VLV.

btw if you think the patch is useful and you've reviewed it according to
the "Reviewer's Statement of Oversight" [1] then please always supply your
reviewed-by tag. Otherwise it's just the informal acked-by.

Patch merged into dinq.

Thanks, Daniel


[1] https://www.kernel.org/doc/Documentation/SubmittingPatches
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  reply	other threads:[~2014-03-22 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:18 [PATCH] drm/i915: Rename GFX_TLB_INVALIDATE_ALWAYS Chris Wilson
2014-03-22  3:29 ` Gupta, Sourab
2014-03-22 11:23   ` Daniel Vetter [this message]
2014-03-23  8:50     ` Gupta, Sourab

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=20140322112356.GD26519@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sourab.gupta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox