From: "Thomas Hellström (Intel)" <thomas_os@shipmail.org>
To: Matthew Brost <matthew.brost@intel.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 0/4] Enable GuC submission by default on DG1
Date: Fri, 6 Aug 2021 13:34:33 +0200 [thread overview]
Message-ID: <b20f28eb-9efc-3d4e-57fa-c52c255063a5@shipmail.org> (raw)
In-Reply-To: <20210803172623.GA82856@DUT151-ICLU.fm.intel.com>
Hi,
On 8/3/21 7:26 PM, Matthew Brost wrote:
> On Tue, Aug 03, 2021 at 02:15:13PM +0200, Daniel Vetter wrote:
>> On Tue, Aug 3, 2021 at 6:53 AM Matthew Brost <matthew.brost@intel.com> wrote:
>>> Minimum set of patches to enable GuC submission on DG1 and enable it by
>>> default.
>>>
>>> A little difficult to test as IGTs do not work with DG1 due to a bunch
>>> of uAPI features being disabled (e.g. relocations, caching memory
>>> options, etc...).
>> Matt Auld has an igt series which fixes a lot of this stuff, would be
>> good to do at least a Test-With run with that.
>>
It looks like Maarten now merged Matt's series to IGT.
There is a series on IGT trybot with pending work to have some igt tests
support relocations,
https://patchwork.freedesktop.org/series/92043/
One of the tests that have WIP fixes is gem_exec_whisper, and that
particular test has historically shown occasional hangs with GuC
submission on DG1 so it would be very desirable if we could make that
test in particular work (I haven't verified that that's the case) reliably.
Also the following series:
https://patchwork.freedesktop.org/series/93455/
tries a bit harder to get some more tests running, squashing the above
series on top of latest IGT.
Thanks,
/Thomas
next prev parent reply other threads:[~2021-08-06 11:44 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-03 5:11 [Intel-gfx] [PATCH 0/4] Enable GuC submission by default on DG1 Matthew Brost
2021-08-03 5:04 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-08-03 5:05 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2021-08-03 5:11 ` [Intel-gfx] [PATCH 1/4] drm/i915: Do not define vma on stack Matthew Brost
2021-08-04 19:37 ` Matthew Brost
2021-08-03 5:11 ` [Intel-gfx] [PATCH 2/4] drm/i915/guc: put all guc objects in lmem when available Matthew Brost
2021-08-06 18:43 ` John Harrison
2021-08-03 5:11 ` [Intel-gfx] [PATCH 3/4] drm/i915/guc: Add DG1 GuC / HuC firmware defs Matthew Brost
2021-08-06 18:43 ` John Harrison
2021-08-03 5:11 ` [Intel-gfx] [PATCH 4/4] drm/i915/guc: Enable GuC submission by default on DG1 Matthew Brost
2021-08-06 18:44 ` John Harrison
2021-08-03 5:27 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-03 12:15 ` [Intel-gfx] [PATCH 0/4] " Daniel Vetter
2021-08-03 17:26 ` Matthew Brost
2021-08-06 11:34 ` Thomas Hellström (Intel) [this message]
2021-08-06 12:07 ` Thomas Hellström (Intel)
2021-08-06 16:09 ` Thomas Hellström (Intel)
2021-08-07 17:20 ` Matthew Brost
2021-08-03 16:22 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=b20f28eb-9efc-3d4e-57fa-c52c255063a5@shipmail.org \
--to=thomas_os@shipmail.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.brost@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;
as well as URLs for NNTP newsgroup(s).