From: Chris Wilson <chris@chris-wilson.co.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
Dave Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/i915/execbuffer: Reorder relocations to match new object order
Date: Thu, 13 Jan 2011 00:48:03 +0000 [thread overview]
Message-ID: <b7da2f$q4ct63@fmsmga001.fm.intel.com> (raw)
In-Reply-To: <AANLkTi=qHW3esgZYq55dgSz15ZDpukXn6zO17nJ1fWzS@mail.gmail.com>
On Wed, 12 Jan 2011 16:27:46 -0800, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Jan 12, 2011 at 4:13 PM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> >
> > This is what I'm running with at the moment. It only appears to affect the
> > slow path which hopefully explains why it is relatively infrequent...
>
> I think you're still missing some case.
>
> This improves the video case a lot - I can't see any artifacts there -
> but I still get occasional corruption when moving between the "share"
> and "rate" buttons, and they end up drawing incorrectly.
Now we're probably drifting into other bug territory... ;-)
I'll look again in the morning. Usually running the conformance test
suites in parallel is enough to exercise the worst-case behaviour.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-01-13 0:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <id:b7da2f$q4c60f@fmsmga001.fm.intel.com>
2011-01-13 0:13 ` [PATCH] drm/i915/execbuffer: Reorder relocations to match new object order Chris Wilson
2011-01-13 0:27 ` Linus Torvalds
2011-01-13 0:48 ` Chris Wilson [this message]
2011-01-13 4:39 ` Linus Torvalds
2011-01-13 11:07 ` [PATCH] drm/i915/execbuffer: Clear domains before beginning reloc processing Chris Wilson
2011-01-13 15:54 ` Linus Torvalds
2011-01-13 16:10 ` Chris Wilson
2011-01-13 20:43 ` Alessandro Suardi
2011-01-14 17:37 ` Linus Torvalds
2011-01-14 18:08 ` Chris Wilson
2011-01-14 22:52 ` Dave Airlie
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='b7da2f$q4ct63@fmsmga001.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.