Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Balasubrawmanian, Vivaik" <vivaik.balasubrawmanian@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events.
Date: Fri, 15 Sep 2023 10:30:44 -0700	[thread overview]
Message-ID: <fdce464e-0fdc-487d-e71a-6cc9373cb22e@intel.com> (raw)
In-Reply-To: <a28eca84-3a55-0e00-6287-48a24de28b94@intel.com>

On 9/14/2023 3:03 PM, Balasubrawmanian, Vivaik wrote:
> On 9/13/2023 3:57 PM, Alan Previn wrote:
>> Debugging PXP issues can't even begin without understanding precedding
>> sequence of events. Add drm_dbg into the most important PXP events.
>>
>>   v2 : - remove __func__ since drm_dbg covers that (Jani).
>>        - add timeout of the restart from front-end (Alan).
>>
>> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
>> ---
>>   drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.c |  2 ++
>>   drivers/gpu/drm/i915/pxp/intel_pxp.c         | 15 ++++++++++++---
>>   drivers/gpu/drm/i915/pxp/intel_pxp_irq.c     |  4 ++--
>>   drivers/gpu/drm/i915/pxp/intel_pxp_session.c |  6 +++++-
>>   drivers/gpu/drm/i915/pxp/intel_pxp_types.h   |  1 +
>>   5 files changed, 22 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.c 
>> b/drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.c
>> index 5f138de3c14f..61216c4abaec 100644
>> --- a/drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.c
>> +++ b/drivers/gpu/drm/i915/gt/uc/intel_gsc_proxy.c
>> @@ -321,6 +321,7 @@ static int i915_gsc_proxy_component_bind(struct 
>> device *i915_kdev,
>>       mutex_lock(&gsc->proxy.mutex);
>>       gsc->proxy.component = data;
>>       gsc->proxy.component->mei_dev = mei_kdev;
>> +    gt_dbg(gt, "GSC proxy mei component bound\n");
>>       mutex_unlock(&gsc->proxy.mutex);
>>   <snip>
>
> Can we move the debug print to outside the mutex block?
>
> review complete conditional to the above fix.
>
> Reviewed-by: Balasubrawmanian, Vivaik 
> <vivaik.balasubrawmanian@intel.com> 
> <mailto:vivaik.balasubrawmanian@intel.com>
>
> <snip>
>
>> base-commit: 45460a37f9be43072b509ca6044b215648f56221
>
>


  parent reply	other threads:[~2023-09-15 17:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 22:57 [Intel-gfx] [PATCH v2 1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events Alan Previn
2023-09-14  1:20 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/1] " Patchwork
2023-09-14  1:35 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
     [not found] ` <a28eca84-3a55-0e00-6287-48a24de28b94@intel.com>
2023-09-15 17:30   ` Balasubrawmanian, Vivaik [this message]
2023-10-11  3:00 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [v2,1/1] drm/i915/pxp: Add drm_dbgs for critical PXP events. (rev2) Patchwork
2023-10-11  3:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-10-11 16:56 ` [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=fdce464e-0fdc-487d-e71a-6cc9373cb22e@intel.com \
    --to=vivaik.balasubrawmanian@intel.com \
    --cc=intel-gfx@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