Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: "Gupta, Anshuman" <anshuman.gupta@intel.com>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Cc: "Roper, Matthew D" <matthew.d.roper@intel.com>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc support
Date: Fri, 19 Jan 2024 17:52:04 +0530	[thread overview]
Message-ID: <9a0b1e1d-7ff8-4d39-a6de-c547033c70f7@intel.com> (raw)
In-Reply-To: <CY5PR11MB6211834CA364535838F7EC8095702@CY5PR11MB6211.namprd11.prod.outlook.com>



On 19-01-2024 15:05, Gupta, Anshuman wrote:
> 
> 
>> -----Original Message-----
>> From: Nilawar, Badal <badal.nilawar@intel.com>
>> Sent: Friday, January 19, 2024 3:01 PM
>> To: Gupta, Anshuman <anshuman.gupta@intel.com>; intel-
>> xe@lists.freedesktop.org
>> Cc: Vivi, Rodrigo <rodrigo.vivi@intel.com>; Roper, Matthew D
>> <matthew.d.roper@intel.com>; Dixit, Ashutosh <ashutosh.dixit@intel.com>;
>> Belgaumkar, Vinay <vinay.belgaumkar@intel.com>
>> Subject: Re: [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc
>> support
>>
>>
>>
>> On 19-01-2024 14:58, Gupta, Anshuman wrote:
>>>
>>>
>>>> -----Original Message-----
>>>> From: Nilawar, Badal <badal.nilawar@intel.com>
>>>> Sent: Friday, January 19, 2024 1:49 PM
>>>> To: intel-xe@lists.freedesktop.org
>>>> Cc: Gupta, Anshuman <anshuman.gupta@intel.com>; Vivi, Rodrigo
>>>> <rodrigo.vivi@intel.com>; Roper, Matthew D
>>>> <matthew.d.roper@intel.com>; Dixit, Ashutosh
>>>> <ashutosh.dixit@intel.com>; Belgaumkar, Vinay
>>>> <vinay.belgaumkar@intel.com>
>>>> Subject: [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc
>>>> support
>>>>
>>>> Expose debugfs entry to check if platform support GuC PC (SLPC) feature.
>>>>
>>>> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
>>>> ---
>>>>    drivers/gpu/drm/xe/xe_debugfs.c | 8 ++++++++
>>>>    1 file changed, 8 insertions(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/xe/xe_debugfs.c
>>>> b/drivers/gpu/drm/xe/xe_debugfs.c index c56fd7d59f05..2f474bf0e7c7
>>>> 100644
>>>> --- a/drivers/gpu/drm/xe/xe_debugfs.c
>>>> +++ b/drivers/gpu/drm/xe/xe_debugfs.c
>>>> @@ -30,6 +30,13 @@ static struct xe_device *node_to_xe(struct
>>>> drm_info_node *node)
>>>>    	return to_xe_device(node->minor->dev);  }
>>>>
>>>> +static int is_gucpc_supported(struct seq_file *m, void *data) {
>>>> +	struct xe_device *xe = node_to_xe(m->private);
>>>> +
>>>> +	return (int)!xe->info.skip_guc_pc;
>>>> +}
>>>> +
>>>>    static int info(struct seq_file *m, void *data)  {
>>>>    	struct xe_device *xe = node_to_xe(m->private); @@ -67,6 +74,7 @@
>>>> static int info(struct seq_file *m, void *data)
>>>>
>>>>    static const struct drm_info_list debugfs_list[] = {
>>>>    	{"info", info, 0},
>>>> +	{"is_gucpc_supported", is_gucpc_supported, 0},
>>> Above debugfs is per device.
>>> We need this debugfs for each gt.
>> The field skip_guc_pc is device specific so kept debugfs device specific.
> That make sense but then it is better to have a print in existing info debugfs
> as this is filed in xe->info ?
>  From igt we can grep the skip_guc_pc either "Yes" or "No".
This make sense. I will update and send new rev.

Thanks,
Badal
> Thanks,
> Anshuman.
> 
>>
>> Regards,
>> Badal
>>> Thanks,
>>> Anshuman.
>>>>    };
>>>>
>>>>    static int forcewake_open(struct inode *inode, struct file *file)
>>>> --
>>>> 2.25.1
>>>

      parent reply	other threads:[~2024-01-19 12:22 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-19  8:18 [PATCH] drm/xe/debugfs: Expose debugfs entry to check guc pc support Badal Nilawar
2024-01-19  8:25 ` Nilawar, Badal
2024-01-19 11:42   ` Jani Nikula
2024-01-19  8:29 ` ✓ CI.Patch_applied: success for " Patchwork
2024-01-19  8:29 ` ✓ CI.checkpatch: " Patchwork
2024-01-19  8:30 ` ✓ CI.KUnit: " Patchwork
2024-01-19  8:37 ` ✓ CI.Build: " Patchwork
2024-01-19  8:37 ` ✓ CI.Hooks: " Patchwork
2024-01-19  8:39 ` ✓ CI.checksparse: " Patchwork
2024-01-19  9:03 ` ✓ CI.BAT: " Patchwork
2024-01-19  9:28 ` [PATCH] " Gupta, Anshuman
2024-01-19  9:31   ` Nilawar, Badal
2024-01-19  9:35     ` Gupta, Anshuman
2024-01-19  9:57       ` Riana Tauro
2024-01-19 12:40         ` Nilawar, Badal
2024-01-19 12:22       ` Nilawar, Badal [this message]

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=9a0b1e1d-7ff8-4d39-a6de-c547033c70f7@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@intel.com \
    --cc=rodrigo.vivi@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