From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Workaround incoherence with fence updates on Valleyview
Date: Wed, 22 May 2013 20:33:27 +0200 [thread overview]
Message-ID: <20130522183327.GD1082@phenom.ffwll.local> (raw)
In-Reply-To: <1369238887-9528-1-git-send-email-chris@chris-wilson.co.uk>
On Wed, May 22, 2013 at 05:08:06PM +0100, Chris Wilson wrote:
> In commit 25ff1195f8a0b3724541ae7bbe331b4296de9c06
> Author: Chris Wilson <chris@chris-wilson.co.uk>
> Date: Thu Apr 4 21:31:03 2013 +0100
>
> drm/i915: Workaround incoherence between fences and LLC across multiple CPUs
>
> we introduced an empirical workaround for memory corruption when using
> fences from multiple CPUs. At the time, we did not have any results for
> Valleyview, so the presumption was that it was limited to recent
> generations using LLC. Now we have evidence that Valleyview also suffers
> incoherence and requires a similar but different workaround. For
> Valleyview, the wbinvd instruction is insufficient and we require the
> serialising register write per-CPU. Conversely, that serialising
> register write is not enough for SNB/IVB/HSW. To compromise and keep the
> code relatively clean, employ both serialisation techniques in the same
> workaround.
>
> Reported-by: Jon Bloomfield <jon.bloomfield@intel.com>
> Tested-by: Jon Bloomfield <jon.bloomfield@intel.com>
> Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=62191
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Queued for -next (since vlv isn't yet declared stable in 3.10), thanks for
the patch.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-05-22 18:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-22 16:08 [PATCH] drm/i915: Workaround incoherence with fence updates on Valleyview Chris Wilson
2013-05-22 18:33 ` 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=20130522183327.GD1082@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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