From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Drop a defunct timeline assertion
Date: Thu, 09 Jan 2020 10:30:30 +0200 [thread overview]
Message-ID: <87sgkpf2vt.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <157855794804.13423.18050306819020127424@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Mika Kuoppala (2020-01-09 08:14:21)
>> Chris Wilson <chris@chris-wilson.co.uk> writes:
>>
>> > intel_timeline_enter() has been decoupled from intel_timeline_pin() and
>> > both enter/exit & pin/unpin are allowed [read expected] to run
>> > concurrently with one another. The assertion that they had better not is
>> > stale.
>> >
>> > Closes: https://gitlab.freedesktop.org/drm/intel/issues/940
>>
>> Hmm I got page not found for this even tho other issues are shown :O
>
> You need to login for this one.
>
>> References to the decoupling part?
>
> References: a6edbca74b30 ("drm/i915/gt: Close race between engine_park and intel_gt_retire_requests")
Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2020-01-09 8:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 14:38 [Intel-gfx] [PATCH] drm/i915/gt: Drop a defunct timeline assertion Chris Wilson
2020-01-07 19:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-08 4:19 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-01-09 8:14 ` [Intel-gfx] [PATCH] " Mika Kuoppala
2020-01-09 8:19 ` Chris Wilson
2020-01-09 8:30 ` Mika Kuoppala [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=87sgkpf2vt.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox