From: Jani Nikula <jani.nikula@linux.intel.com>
To: Arun Siluvery <arun.siluvery@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Update ring space correctly on lrc context reset
Date: Tue, 13 Oct 2015 16:02:02 +0300 [thread overview]
Message-ID: <8737xe6hx1.fsf@intel.com> (raw)
In-Reply-To: <55E6DB99.5050305@linux.intel.com>
On Wed, 02 Sep 2015, Arun Siluvery <arun.siluvery@linux.intel.com> wrote:
> On 20/08/2015 16:27, Chris Wilson wrote:
>> On Thu, Aug 20, 2015 at 05:34:59PM +0300, Mika Kuoppala wrote:
>>> If we leave the last_retired_head to pre-reset value, we might
>>> end up in a situation where intel_ring_space() returns wrong
>>> value on next hardware init.
>>
>> http://patchwork.freedesktop.org/patch/46612/
>> and earlier
>> -Chris
>>
> Hi Chris,
>
> I see the warning even with below batch,
>
> [Intel-gfx] [PATCH 50/70] drm/i915: The argument for postfix is redundant
> http://patchwork.freedesktop.org/patch/46601/
>
> the following patch need to be updated as it uses olr,
> [Intel-gfx] [PATCH 51/70] drm/i915: Record the position of the start of
> the request
> http://patchwork.freedesktop.org/patch/46612/
>
> Do we need some of the previous patches in series as well?
>
> This patch is fixing the issue in the current code, do you think we can
> get this in its current state?
Is this patch still valid?
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-10-13 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 14:34 [PATCH] drm/i915: Update ring space correctly on lrc context reset Mika Kuoppala
2015-08-20 15:27 ` Chris Wilson
2015-09-02 11:20 ` Arun Siluvery
2015-10-13 13:02 ` Jani Nikula [this message]
2015-10-23 10:39 ` Mika Kuoppala
2015-10-23 10:51 ` 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=8737xe6hx1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=arun.siluvery@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
/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