[Intel-gfx] [PATCH v4 3/5] drm/i915/guc: Implement dynamic WOPCM partitioning

Yaodong Li yaodong.li at intel.com
Wed Dec 13 18:19:06 UTC 2017


On 12/13/2017 01:11 AM, Joonas Lahtinen wrote:
> On Tue, 2017-12-12 at 14:56 -0800, Jackie Li wrote:
>> Hardware may have specific restrictions on GuC WOPCM partition
>> size versus HuC firmware size. With static WOPCM partitioning,
>> there's no way to adjust the GuC WOPCM partition size based on
>> the actual HuC firmware size, so that GuC/HuC loading failure
>> would occur even if there was enough WOPCM space for both
>> GuC and HuC firmware.
> WOPCM being a shared feature of the hardware, it should not go under
> intel_guc_ prefix.
>
> There should be a clear division of what is specific to GuC feature
> only and what is just a feature that happens to be used by GuC (and
> equally can be used by HuC too).
the intel_guc_wopcm here only refers to the wopcm used by
GuC, this structure only defines the GuC related wopcm info.
(wopcm partition for GuC). We only need to set these values
(defined in this structure) to GuC registers. And this structure
should never be touched if GuC was disabled. so it should be
a part of GuC.

Regards, Jackie
>
> Regards, Joonas



More information about the Intel-gfx mailing list