From: John Harrison <john.c.harrison@intel.com>
To: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: Eero Tamminen <eero.t.tamminen@intel.com>
Subject: Re: [PATCH] drm/xe/gsc: Make GSCCS disabling message less alarming
Date: Thu, 19 Dec 2024 14:17:02 -0800 [thread overview]
Message-ID: <f723a730-6fde-4d65-ad29-b86018cbc768@intel.com> (raw)
In-Reply-To: <3b515ac4-9404-458d-a734-831d84accff2@intel.com>
On 12/19/2024 13:06, Daniele Ceraolo Spurio wrote:
> On 12/18/2024 5:51 PM, John Harrison wrote:
>> On 12/18/2024 17:09, Daniele Ceraolo Spurio wrote:
>>> The GSCCS is only used to transport messages from the driver to the GSC
>>> FW; therefore, we can disable it if we're not using the FW, which is
>>> the case on both BMG and PTL. However, the current wording of the
>>> logged
>>> message could be interpreted as a problem, so reword to make it clearer
>>> it is not an error and lower it debug verbosity as users don't really
>>> need to know about it.
>>>
>>> Reported-by: Eero Tamminen <eero.t.tamminen@intel.com>
>>> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/3866
>>> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
>>> ---
>>> drivers/gpu/drm/xe/xe_hw_engine.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/xe/xe_hw_engine.c
>>> b/drivers/gpu/drm/xe/xe_hw_engine.c
>>> index 4294aa600192..ac9c666a9652 100644
>>> --- a/drivers/gpu/drm/xe/xe_hw_engine.c
>>> +++ b/drivers/gpu/drm/xe/xe_hw_engine.c
>>> @@ -775,7 +775,7 @@ static void check_gsc_availability(struct xe_gt
>>> *gt)
>>> xe_mmio_write32(>->mmio, GUNIT_GSC_INTR_ENABLE, 0);
>>> xe_mmio_write32(>->mmio, GUNIT_GSC_INTR_MASK, ~0);
>>> - drm_info(&xe->drm, "gsccs disabled due to lack of FW\n");
>>> + drm_dbg(&xe->drm, "GSC FW not used, disabling gsccs\n");
>> This message would also be hit in the case where the firmware is
>> supposed to be present but isn't. E.g. on a LNL but without the right
>> firmware package installed? But presumably in that case, there would
>> already have been an earlier message about missing firmware files?
>
> Right now if the firmware is missing we abort the driver load, so we
> don't even get this far. If that were to change (and the code here
> does for this purpose support the case where the FW is defined but
> missing) I'd expect we'd get an earlier error about the missing blob.
>
> Daniele
Sounds good.
Reviewed-by: John Harrison <John.C.Harrison@Intel.com>
>
>>
>> John.
>>
>>> }
>>> }
>>
>
next prev parent reply other threads:[~2024-12-19 22:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 1:09 [PATCH] drm/xe/gsc: Make GSCCS disabling message less alarming Daniele Ceraolo Spurio
2024-12-19 1:51 ` John Harrison
2024-12-19 21:06 ` Daniele Ceraolo Spurio
2024-12-19 22:17 ` John Harrison [this message]
2024-12-19 5:11 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-19 5:11 ` ✓ CI.checkpatch: " Patchwork
2024-12-19 5:12 ` ✓ CI.KUnit: " Patchwork
2024-12-19 5:30 ` ✓ CI.Build: " Patchwork
2024-12-19 5:32 ` ✓ CI.Hooks: " Patchwork
2024-12-19 5:34 ` ✓ CI.checksparse: " Patchwork
2024-12-19 9:47 ` ✓ CI.BAT: " Patchwork
2024-12-20 9:13 ` ✗ Xe.CI.Full: 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=f723a730-6fde-4d65-ad29-b86018cbc768@intel.com \
--to=john.c.harrison@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=eero.t.tamminen@intel.com \
--cc=intel-xe@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