public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Clear domains before beginning reloc processing
Date: Thu, 13 Jan 2011 16:10:59 +0000	[thread overview]
Message-ID: <1bdc18$j8l825@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <AANLkTimypim707rEXaPBaKoGgGmz3Of4EmPNw7VokJL6@mail.gmail.com>

On Thu, 13 Jan 2011 07:54:59 -0800, Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, Jan 13, 2011 at 3:07 AM, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> > After reordering the sequence of relocating objects, commit 6fe4f1404,
> > we can no longer rely on seeing all reloc targets prior to performing
> > the relocation. So we need to clear the relocation domains earlier.
> 
> Yup, this one (together with the previous fix) seems to get rid of all
> the artifacts.
> 
> Should I just apply them as patches, or do you have a git branch to pull from?

They will be in drm-intel-fixes. There have been a couple of other patches,
for the compiler warning, the typo that Indan spotted and for modparam to
workaround the U160, so I'll send the pull request it via Dave.
-Chris

$ git shortlog linus..upstream/drm-intel-fixes
Chris Wilson (5):
      drm/i915/debugfs: Correct format after changing type of err object 'size'
      drm/i915: Add a module option to override the use of SSC
      drm/i915: Fix error handler to capture the first batch after the seqno
      drm/i915/execbuffer: Reorder relocations to match new object order
      drm/i915/execbuffer: Clear domains before beginning reloc processing

Indan Zupancic (1):
      drm/i915/panel: The backlight is enabled if the current value is non-zero

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-01-13 16:12 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
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 [this message]
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='1bdc18$j8l825@fmsmga002.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox