From: youling 257 <youling257@gmail.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [CI 2/2] drm/i915/gt: Track engine round-trip times
Date: Sat, 8 Feb 2020 00:42:32 +0800 [thread overview]
Message-ID: <CAOzgRdbuR_wE77HKTcRr=irqTs3EP6CXMuRY_RZ6WACQwgL-Ag@mail.gmail.com> (raw)
In-Reply-To: <158109328469.16098.11014223815188039767@skylake-alporthouse-com>
That's my build many times test boot result.
https://github.com/youling257/android-4.9/commits/drm-intel
the "drm/i915/gt: Track engine round-trip times" is bad commit for my
Androidx86.
2020-02-08 0:34 GMT+08:00, Chris Wilson <chris@chris-wilson.co.uk>:
> Quoting youling257 (2020-02-07 16:31:25)
>> This patch cause GPU hang on my Bay trail z3735f.
>> https://gitlab.freedesktop.org/drm/intel/issues/1144
>
> No it didn't. The cause for that is unfortunately well known.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-02-07 17:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 12:43 [Intel-gfx] [CI 1/2] drm/i915/gt: Schedule request retirement when signaler idles Chris Wilson
2019-12-19 12:43 ` [Intel-gfx] [CI 2/2] drm/i915/gt: Track engine round-trip times Chris Wilson
2020-02-07 16:31 ` youling257
2020-02-07 16:34 ` Chris Wilson
2020-02-07 16:42 ` youling 257 [this message]
2020-02-07 16:48 ` youling 257
2020-02-08 21:11 ` youling 257
2019-12-19 15:58 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [CI,1/2] drm/i915/gt: Schedule request retirement when signaler idles Patchwork
2019-12-19 16:50 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
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='CAOzgRdbuR_wE77HKTcRr=irqTs3EP6CXMuRY_RZ6WACQwgL-Ag@mail.gmail.com' \
--to=youling257@gmail.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;
as well as URLs for NNTP newsgroup(s).