All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [CI 3/5] drm/i915: Disable semaphores on Sandybridge
Date: Tue, 21 Nov 2017 12:23:44 +0200	[thread overview]
Message-ID: <87ine4udzj.fsf@intel.com> (raw)
In-Reply-To: <151125876734.27169.15416572182330089050@mail.alporthouse.com>

On Tue, 21 Nov 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
> Quoting Jani Nikula (2017-11-21 09:57:30)
>> On Mon, 20 Nov 2017, Chris Wilson <chris@chris-wilson.co.uk> wrote:
>> > I should have admitted defeat long ago as there has been a rare but
>> > persistent error on Sandybridge where semaphore signaling did not
>> > propagate to the waiter, leading to a GPU hang.
>> 
>> I'm late to the party, but I think the choice of patch ordering here is
>> a bit unfortunate. Or is it intentional that you can't backport this to
>> stable as-is?
>
> The unmentioned problem with this patch, is that we were using
> semaphores to mask the missed-breadcrumb-syndrome on Sandybridge (and
> that without semaphores we are even more at risk). So I am not too
> concerned in backporting this particular patch further than we are able
> to inspect ourselves.

Should I read between the lines that "the missed-breadcrumb-syndrome"
has been fixed in dinq?

Sounds reasonable. Let's hope this doesn't get picked up by the stable
backport autoselection...

BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2017-11-21 10:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-20 20:55 [CI 1/5] drm/i915: Remove i915.enable_execlists module parameter Chris Wilson
2017-11-20 20:55 ` [CI 2/5] drm/i915: Remove obsolete ringbuffer emission for gen8+ Chris Wilson
2017-11-20 20:55 ` [CI 3/5] drm/i915: Disable semaphores on Sandybridge Chris Wilson
2017-11-21  9:57   ` Jani Nikula
2017-11-21 10:06     ` Chris Wilson
2017-11-21 10:23       ` Jani Nikula [this message]
2017-11-21 10:39         ` Chris Wilson
2017-11-20 20:55 ` [CI 4/5] drm/i915: Move debugfs/i915_semaphore_status to i915_engine_info Chris Wilson
2017-11-20 20:55 ` [CI 5/5] drm/i915: Remove i915.semaphores modparam Chris Wilson
2017-11-20 21:40 ` ✓ Fi.CI.BAT: success for series starting with [CI,1/5] drm/i915: Remove i915.enable_execlists module parameter Patchwork
2017-11-20 22:46 ` ✗ Fi.CI.IGT: warning " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2017-11-20 16:04 [CI 1/5] " Chris Wilson
2017-11-20 16:04 ` [CI 3/5] drm/i915: Disable semaphores on Sandybridge 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=87ine4udzj.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --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 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.