From: John Harrison <John.C.Harrison@Intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
Intel-GFX@Lists.FreeDesktop.Org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/guc: Update to GuC FW v40
Date: Wed, 15 Jan 2020 11:49:30 -0800 [thread overview]
Message-ID: <3e84b0d5-d324-c513-51f9-fdfe46a16075@Intel.com> (raw)
In-Reply-To: <3201a276-52d7-3140-6271-3cf6c5bd7dda@intel.com>
On 1/15/2020 11:45, Daniele Ceraolo Spurio wrote:
> On 1/14/20 6:40 PM, John.C.Harrison@Intel.com wrote:
>> From: Matthew Brost <matthew.brost@intel.com>
>>
>> The GuC major version has jumped from 35 to 40. This is because this
>> FW includes a significant re-write of the API that completely breaks
>> backwards compatibility for command submission. This patch is
>> sufficient to enable loading of the GuC and hence authentication of
>> the HuC. Support of command submission will follow in a much larger
>> patch series.
>>
>> The changes required to load v40 FW are:
>> * An additional data structure and associated 'private_data' pointer
>> are now required to be setup by the driver. This is basically a
>> scratch area of memory that the GuC owns. The size is read from the
>> CSS header.
>>
>> * A physical to logical engine mapping table is required to be
>> provided in the GuC additional data structure. This is initialized
>> with a 1 to 1 mapping.
>>
>> * GUC_CTL_CTXINFO has been removed from the initialization params.
>>
>
> You're missing the removal of ads.reg_state_buffer, which is several
> page of memory we can now save. Michal has floated a patch for that
> internally.
>
> Daniele
>
Yes, I just noticed that a little earlier. Already in the process of
squashing it in.
John.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-15 19:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 2:40 [Intel-gfx] [PATCH] drm/i915/guc: Update to GuC FW v40 John.C.Harrison
2020-01-15 3:24 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-15 3:24 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-15 19:45 ` [Intel-gfx] [PATCH] " Daniele Ceraolo Spurio
2020-01-15 19:49 ` John Harrison [this message]
2020-01-15 20:37 ` [Intel-gfx] [PATCH v2] " John.C.Harrison
2020-01-21 18:29 ` Daniele Ceraolo Spurio
2020-01-21 18:40 ` John Harrison
2020-01-15 21:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/guc: Update to GuC FW v40 (rev2) Patchwork
2020-01-15 21:23 ` [Intel-gfx] ✗ Fi.CI.BUILD: warning " Patchwork
2020-01-17 10:12 ` [Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/guc: Update to GuC FW v40 Patchwork
2020-01-18 9:25 ` [Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/guc: Update to GuC FW v40 (rev2) Patchwork
2020-01-21 19:09 ` [Intel-gfx] [CI v2 1/2] drm/i915/guc: Update to GuC FW v40 John.C.Harrison
2020-01-21 19:09 ` [Intel-gfx] [CI v2 2/2] Hack for CI: enable HuC loading by default John.C.Harrison
2020-01-21 19:57 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/guc: Update to GuC FW v40 (rev3) Patchwork
2020-01-21 20:23 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-23 2:24 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2020-01-23 21:35 ` John Harrison
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=3e84b0d5-d324-c513-51f9-fdfe46a16075@Intel.com \
--to=john.c.harrison@intel.com \
--cc=Intel-GFX@Lists.FreeDesktop.Org \
--cc=daniele.ceraolospurio@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).