Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: John Harrison <john.c.harrison@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
	<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Make force_reset attributes write-only
Date: Mon, 9 Jun 2025 15:13:28 -0700	[thread overview]
Message-ID: <c9ff6291-82a6-4412-80e1-1d9cdaf8a55e@intel.com> (raw)
In-Reply-To: <20250603192218.637-1-michal.wajdeczko@intel.com>

On 6/3/2025 12:22 PM, Michal Wajdeczko wrote:
> Stop supporting triggering GT resets from readoperations, as main
> user of this feature (IGT) already switched to use write operation.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: John Harrison <John.C.Harrison@Intel.com>
> ---
>   drivers/gpu/drm/xe/xe_gt_debugfs.c | 10 ++--------
>   1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt_debugfs.c b/drivers/gpu/drm/xe/xe_gt_debugfs.c
> index 848618acdca8..3afd0d58fa6b 100644
> --- a/drivers/gpu/drm/xe/xe_gt_debugfs.c
> +++ b/drivers/gpu/drm/xe/xe_gt_debugfs.c
> @@ -349,9 +349,6 @@ static ssize_t force_reset_write(struct file *file,
>   
>   static int force_reset_show(struct seq_file *s, void *unused)
>   {
> -	struct xe_gt *gt = s->private;
> -
> -	force_reset(gt); /* to be deprecated! */
>   	return 0;
>   }
>   DEFINE_SHOW_STORE_ATTRIBUTE(force_reset);
> @@ -377,9 +374,6 @@ static ssize_t force_reset_sync_write(struct file *file,
>   
>   static int force_reset_sync_show(struct seq_file *s, void *unused)
>   {
> -	struct xe_gt *gt = s->private;
> -
> -	force_reset_sync(gt); /* to be deprecated! */
>   	return 0;
>   }
>   DEFINE_SHOW_STORE_ATTRIBUTE(force_reset_sync);
Is the show function still needed for either of these if they are now 
read only?

John.

> @@ -408,8 +402,8 @@ void xe_gt_debugfs_register(struct xe_gt *gt)
>   	root->d_inode->i_private = gt;
>   
>   	/* VF safe */
> -	debugfs_create_file("force_reset", 0600, root, gt, &force_reset_fops);
> -	debugfs_create_file("force_reset_sync", 0600, root, gt, &force_reset_sync_fops);
> +	debugfs_create_file("force_reset", 0200, root, gt, &force_reset_fops);
> +	debugfs_create_file("force_reset_sync", 0200, root, gt, &force_reset_sync_fops);
>   
>   	drm_debugfs_create_files(vf_safe_debugfs_list,
>   				 ARRAY_SIZE(vf_safe_debugfs_list),


  parent reply	other threads:[~2025-06-09 22:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-03 19:22 [PATCH] drm/xe: Make force_reset attributes write-only Michal Wajdeczko
2025-06-03 19:58 ` ✓ CI.Patch_applied: success for " Patchwork
2025-06-03 19:58 ` ✓ CI.checkpatch: " Patchwork
2025-06-03 19:59 ` ✗ CI.KUnit: failure " Patchwork
2025-06-04 17:55 ` ✓ CI.Patch_applied: success for drm/xe: Make force_reset attributes write-only (rev2) Patchwork
2025-06-04 17:55 ` ✓ CI.checkpatch: " Patchwork
2025-06-04 17:56 ` ✓ CI.KUnit: " Patchwork
2025-06-04 18:07 ` ✓ CI.Build: " Patchwork
2025-06-04 18:10 ` ✓ CI.Hooks: " Patchwork
2025-06-04 18:11 ` ✓ CI.checksparse: " Patchwork
2025-06-04 19:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-06-05 15:53 ` ✗ Xe.CI.Full: failure " Patchwork
2025-06-09 22:13 ` John Harrison [this message]
2025-06-24 20:40   ` [PATCH] drm/xe: Make force_reset attributes write-only Michal Wajdeczko

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=c9ff6291-82a6-4412-80e1-1d9cdaf8a55e@intel.com \
    --to=john.c.harrison@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@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