From: Pavel Machek <pavel@ucw.cz>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org,
Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 1/2] drm/i915/gem: Replace reloc chain with terminator on error unwind
Date: Wed, 19 Aug 2020 19:23:31 +0200 [thread overview]
Message-ID: <20200819172331.GA4796@amd> (raw)
In-Reply-To: <20200819103952.19083-1-chris@chris-wilson.co.uk>
[-- Attachment #1: Type: text/plain, Size: 726 bytes --]
Hi!
> If we hit an error during construction of the reloc chain, we need to
> replace the chain into the next batch with the terminator so that upon
> flushing the relocations so far, we do not execute a hanging batch.
Thanks for the patches. I assume this should fix problem from
"5.9-rc1: graphics regression moved from -next to mainline" thread.
I have applied them over current -next, and my machine seems to be
working so far (but uptime is less than 30 minutes).
If the machine still works tommorow, I'll assume problem is solved.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2020-08-19 17:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:39 [PATCH 1/2] drm/i915/gem: Replace reloc chain with terminator on error unwind Chris Wilson
2020-08-19 10:39 ` [PATCH 2/2] drm/i915/gem: Fallback to using a plain kmap if reloc address space is limited Chris Wilson
2020-08-19 17:23 ` Pavel Machek [this message]
2020-08-19 17:36 ` [PATCH 1/2] drm/i915/gem: Replace reloc chain with terminator on error unwind Chris Wilson
2020-08-19 19:33 ` Pavel Machek
2020-08-19 19:40 ` Chris Wilson
2020-08-19 19:47 ` Pavel Machek
2020-08-19 19:52 ` [Intel-gfx] " Chris Wilson
2020-08-20 7:36 ` Chris Wilson
2020-09-08 22:23 ` Pavel Machek
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=20200819172331.GA4796@amd \
--to=pavel@ucw.cz \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@linux.intel.com \
--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