public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Dave Airlie <airlied@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	stable@vger.kernel.org
Subject: Re: [PATCH] drm/i915: disable cpu relocs on ilk and earlier
Date: Mon, 15 Oct 2012 08:11:19 -0700	[thread overview]
Message-ID: <20121015151119.GB30606@kroah.com> (raw)
In-Reply-To: <1350288682-6236-1-git-send-email-daniel.vetter@ffwll.ch>

On Mon, Oct 15, 2012 at 10:11:22AM +0200, Daniel Vetter wrote:
> Hi Greg&stable-team,
> 
> The below patch papers over a graphics corruption issue in 3.5/3.6. The
> regression happened due to pwrite tunings in 3.5, which made cpu relocations
> much more likely.
> 
> The issue seems to have disappeared in 3.7-rc1, but it takes a few days to test
> a patch, so we haven't figured out what exactly fixed things. Now users are
> taking out their pitchforks already, so instead of wasting more days (maybe
> weeks?) to fully understand the bug before backporting the fix, we've opted for
> the below disable patch, which should have minimal impact (at most it undoes the
> tuning improvements in 3.5).
> 
> Patch is tested by reporters & acked by all relevant ppl, please apply to
> 3.5/3.6 series kernels.

No, I'd really like to wait until you figure out what is happening in
3.7-rc1 right now before applying the patch.  We have the rule, "it must
be in Linus's tree first" for a very good reason :)

So, I'll hold onto this until you say what's up with 3.7-rc1, ok?

thanks,

greg k-h

  reply	other threads:[~2012-10-15 15:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-15  8:11 [PATCH] drm/i915: disable cpu relocs on ilk and earlier Daniel Vetter
2012-10-15 15:11 ` Greg KH [this message]
2012-10-15 17:16   ` Daniel Vetter
2012-10-15 17:34     ` Greg KH
2012-10-18  7:34   ` Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2012-10-10  8:06 Daniel Vetter
2012-10-10  9:13 ` 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=20121015151119.GB30606@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=airlied@gmail.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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