From: "Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: dri-devel@lists.freedesktop.org,
Alan Previn <alan.previn.teres.alexis@intel.com>
Subject: Re: [Intel-gfx] [PATCH 1/7] drm/i915/huc: only load HuC on GTs that have VCS engines
Date: Fri, 23 Sep 2022 08:41:08 -0700 [thread overview]
Message-ID: <f0a77865-265c-6d65-df34-d2d76960d64e@intel.com> (raw)
In-Reply-To: <b6d78e11-f0f7-de86-e5c3-e2a12fe55203@linux.intel.com>
On 9/23/2022 3:53 AM, Tvrtko Ursulin wrote:
>
> On 22/09/2022 23:11, Daniele Ceraolo Spurio wrote:
>> On MTL the primary GT doesn't have any media capabilities, so no video
>> engines and no HuC. We must therefore skip the HuC fetch and load on
>> that specific case. Given that other multi-GT platforms might have HuC
>> on the primary GT, we can't just check for that and it is easier to
>> instead check for the lack of VCS engines.
>>
>> Based on code from Aravind Iddamsetty
>>
>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>> Cc: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
>> Cc: John Harrison <john.c.harrison@intel.com>
>> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
>> ---
>> drivers/gpu/drm/i915/gt/uc/intel_huc.c | 21 +++++++++++++++++++++
>> drivers/gpu/drm/i915/i915_drv.h | 9 ++++++---
>> 2 files changed, 27 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_huc.c
>> b/drivers/gpu/drm/i915/gt/uc/intel_huc.c
>> index 3bb8838e325a..d4e2b252f16c 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_huc.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_huc.c
>> @@ -42,12 +42,33 @@
>> * HuC-specific commands.
>> */
>> +static bool vcs_supported(struct intel_gt *gt)
>> +{
>> + intel_engine_mask_t mask = gt->info.engine_mask;
>> +
>> + /*
>> + * we can reach here from i915_driver_early_probe for primary
>> + * GT with it being not fully setup hence fall back to the
>> device info's
>> + * engine mask
>> + */
>> + if (!mask && gt_is_root(gt))
>> + mask = RUNTIME_INFO(gt->i915)->platform_engine_mask;
>
> Is it possible for all instances to be fused off? Wondering if the
> function shouldn't just use platform_engine_mask.
The spec says that there is always going to be at least 1 VCS (bspec
55417 in case you want to double-check). I don't see that changing in
the future, because what's the point of having a media GT if you don't
have any enabled VCS engines on it?
Also, platform_engine_mask only contains the entries of the primary GT,
for the other GTs we'd have to navigate the array in the device info
structure and I don't think we want to do that from here when we've
already copied the mask inside gt->info.engine_mask.
Daniele
>
> Regards,
>
> Tvrtko
>
>> +
>> + return __ENGINE_INSTANCES_MASK(mask, VCS0, I915_MAX_VCS);
>> +}
>> +
>> void intel_huc_init_early(struct intel_huc *huc)
>> {
>> struct drm_i915_private *i915 = huc_to_gt(huc)->i915;
>> + struct intel_gt *gt = huc_to_gt(huc);
>> intel_uc_fw_init_early(&huc->fw, INTEL_UC_FW_TYPE_HUC);
>> + if (!vcs_supported(gt)) {
>> + intel_uc_fw_change_status(&huc->fw,
>> INTEL_UC_FIRMWARE_NOT_SUPPORTED);
>> + return;
>> + }
>> +
>> if (GRAPHICS_VER(i915) >= 11) {
>> huc->status.reg = GEN11_HUC_KERNEL_LOAD_INFO;
>> huc->status.mask = HUC_LOAD_SUCCESSFUL;
>> diff --git a/drivers/gpu/drm/i915/i915_drv.h
>> b/drivers/gpu/drm/i915/i915_drv.h
>> index 134fc1621821..8ca575202e5d 100644
>> --- a/drivers/gpu/drm/i915/i915_drv.h
>> +++ b/drivers/gpu/drm/i915/i915_drv.h
>> @@ -777,12 +777,15 @@ IS_SUBPLATFORM(const struct drm_i915_private
>> *i915,
>> #define __HAS_ENGINE(engine_mask, id) ((engine_mask) & BIT(id))
>> #define HAS_ENGINE(gt, id) __HAS_ENGINE((gt)->info.engine_mask, id)
>> -#define ENGINE_INSTANCES_MASK(gt, first, count) ({ \
>> +#define __ENGINE_INSTANCES_MASK(mask, first, count) ({ \
>> unsigned int first__ = (first); \
>> unsigned int count__ = (count); \
>> - ((gt)->info.engine_mask & \
>> - GENMASK(first__ + count__ - 1, first__)) >> first__; \
>> + ((mask) & GENMASK(first__ + count__ - 1, first__)) >> first__; \
>> })
>> +
>> +#define ENGINE_INSTANCES_MASK(gt, first, count) \
>> + __ENGINE_INSTANCES_MASK((gt)->info.engine_mask, first, count)
>> +
>> #define RCS_MASK(gt) \
>> ENGINE_INSTANCES_MASK(gt, RCS0, I915_MAX_RCS)
>> #define BCS_MASK(gt) \
next prev parent reply other threads:[~2022-09-23 15:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 22:11 [Intel-gfx] [PATCH 0/7] drm/i915: prepare for uC loading on MTL Daniele Ceraolo Spurio
2022-09-22 22:11 ` [Intel-gfx] [PATCH 1/7] drm/i915/huc: only load HuC on GTs that have VCS engines Daniele Ceraolo Spurio
2022-09-23 10:53 ` Tvrtko Ursulin
2022-09-23 15:41 ` Ceraolo Spurio, Daniele [this message]
2022-09-26 16:15 ` Tvrtko Ursulin
2022-09-26 16:28 ` Ceraolo Spurio, Daniele
2022-09-27 9:58 ` Iddamsetty, Aravind
2022-09-22 22:11 ` [Intel-gfx] [PATCH 2/7] drm/i915/uc: fetch uc firmwares for each GT Daniele Ceraolo Spurio
2022-09-30 22:49 ` John Harrison
2022-09-22 22:11 ` [Intel-gfx] [PATCH 3/7] drm/i915/uc: use different ggtt pin offsets for uc loads Daniele Ceraolo Spurio
2022-09-30 23:24 ` John Harrison
2022-09-30 23:42 ` Ceraolo Spurio, Daniele
2022-10-10 19:18 ` John Harrison
2022-09-22 22:11 ` [Intel-gfx] [PATCH 4/7] drm/i915/guc: Add GuC deprivilege feature to MTL Daniele Ceraolo Spurio
2022-09-30 23:33 ` John Harrison
2022-09-22 22:11 ` [Intel-gfx] [PATCH 5/7] drm/i915/mtl: Handle wopcm per-GT and limit calculations Daniele Ceraolo Spurio
2022-09-23 9:24 ` Jani Nikula
2022-09-23 15:34 ` Ceraolo Spurio, Daniele
2022-09-22 22:11 ` [Intel-gfx] [PATCH 6/7] drm/i915/guc: define media GT GuC send regs Daniele Ceraolo Spurio
2022-10-01 0:26 ` John Harrison
2022-09-22 22:11 ` [Intel-gfx] [PATCH 7/7] drm/i915/guc: handle interrupts from media GuC Daniele Ceraolo Spurio
2022-09-28 0:10 ` Matt Roper
2022-09-28 0:22 ` Ceraolo Spurio, Daniele
2022-09-28 18:07 ` Matt Roper
2022-09-28 18:25 ` Ceraolo Spurio, Daniele
2022-09-23 1:12 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: prepare for uC loading on MTL Patchwork
2022-09-23 1:12 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-09-23 1:31 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-09-23 9:24 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=f0a77865-265c-6d65-df34-d2d76960d64e@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tvrtko.ursulin@linux.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