public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 4/6] drm/i915: Serialize all register access
Date: Mon, 15 Jul 2013 20:20:07 -0700	[thread overview]
Message-ID: <20130716032007.GA634@bwidawsk.net> (raw)
In-Reply-To: <20130712205246.GG23323@cantiga.alporthouse.com>

On Fri, Jul 12, 2013 at 09:52:46PM +0100, Chris Wilson wrote:
> On Fri, Jul 12, 2013 at 01:37:28PM -0700, Ben Widawsky wrote:
> > On Fri, Jul 12, 2013 at 03:02:34PM +0100, Chris Wilson wrote:
> > > In theory, the different register blocks were meant to be only ever
> > > touched when holding either the struct_mutex, mode_config.lock or even a
> > > specific localised lock. This does not seem to be the case, and the
> > > hardware reacts extremely badly if we attempt to concurrently access two
> > > registers within the same cacheline.
> > > 
> > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=63914
> > > Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> > 
> > You are crossing the point of no return here for doing this only on HSW
> > where the bug is known to exist. As you are the resident performance
> > curmudgeon I'll defer to you if that's okay or not... just pointing it
> > out.
> 
> I looked at all the extra checks we are doing in addition to just
> reading/writing the register and thought it would be better to close any
> races there. Hence why I think this is a correctness fix above and
> beyond the hsw issue.
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre

Oh, one more thing on this patch... can you please add a Wa comment
marker in the code. I don't have a name for this wa, but if you can't
find anything in the wa database, just call it whatever you feel like,
so long as the tool will pick it up.

-- 
Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2013-07-16  3:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 14:02 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 14:02 ` [PATCH 2/6] drm/i915: Use a private interface for register access within GT Chris Wilson
2013-07-12 20:25   ` Ben Widawsky
2013-07-12 20:55     ` Chris Wilson
2013-07-12 20:57       ` Daniel Vetter
2013-07-12 14:02 ` [PATCH 3/6] drm/i915: Use the common register access functions for NOTRACE variants Chris Wilson
2013-07-12 20:34   ` Ben Widawsky
2013-07-12 20:51     ` Chris Wilson
2013-07-12 14:02 ` [PATCH 4/6] drm/i915: Serialize all register access Chris Wilson
2013-07-12 20:37   ` Ben Widawsky
2013-07-12 20:52     ` Chris Wilson
2013-07-16  3:20       ` Ben Widawsky [this message]
2013-07-12 14:02 ` [PATCH 5/6] drm/i915: Squash gen lookup through multiple indirections inside GT access Chris Wilson
2013-07-12 14:02 ` [PATCH 6/6] drm/i915: Convert the register access tracepoint to be conditional Chris Wilson
  -- strict thread matches above, loose matches on Subject: below --
2013-07-12 14:59 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 14:59 ` [PATCH 4/6] drm/i915: Serialize all register access Chris Wilson
2013-07-12 17:08 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-12 17:08 ` [PATCH 4/6] drm/i915: Serialize all register access Chris Wilson
2013-07-14 20:23   ` Ben Widawsky
2013-07-16 16:16     ` Chris Wilson
2013-07-16 19:02 [PATCH 1/6] drm/i915: Colocate all GT access routines in the same file Chris Wilson
2013-07-16 19:02 ` [PATCH 4/6] drm/i915: Serialize all register access 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=20130716032007.GA634@bwidawsk.net \
    --to=ben@bwidawsk.net \
    --cc=chris@chris-wilson.co.uk \
    --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