Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH v8 2/3] drm/xe: Notify Userspace when gt reset fails
Date: Wed, 26 Jul 2023 10:39:23 -0400	[thread overview]
Message-ID: <ZMEwG8O9dZ8Ri7Kc@intel.com> (raw)
In-Reply-To: <20230725155115.3759312-3-himal.prasad.ghimiray@intel.com>

On Tue, Jul 25, 2023 at 09:21:14PM +0530, Himal Prasad Ghimiray wrote:
> Send uevent in case of gt reset failure. This intimation can be used by
> userspace monitoring tool to do the device level reset/reboot
> when GT reset fails. udevadm can be used to monitor the uevents.
> 
> v2:
> - Support only gt failure notification (Rodrigo)
> 
> v3
> - Rectify the comments in header file.
> 
> v4
> - Use pci kobj instead of drm kobj for notification.(Rodrigo)
> - Cleanup (Badal)
> 
> Cc: Aravind Iddamsetty <aravind.iddamsetty@intel.com>
> Cc: Tejas Upadhyay <tejas.upadhyay@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Reviewed-by: Badal Nilawar <badal.nilawar@intel.com>
> Signed-off-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

Cc: Matt Roper Matt Roper <matthew.d.roper@intel.com>

> ---
>  drivers/gpu/drm/xe/xe_gt.c | 17 +++++++++++++++++
>  include/uapi/drm/xe_drm.h  |  8 ++++++++
>  2 files changed, 25 insertions(+)
> 
> diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
> index 3e32d38aeeea..f4766fb6bfdb 100644
> --- a/drivers/gpu/drm/xe/xe_gt.c
> +++ b/drivers/gpu/drm/xe/xe_gt.c
> @@ -8,6 +8,7 @@
>  #include <linux/minmax.h>
>  
>  #include <drm/drm_managed.h>
> +#include <drm/xe_drm.h>
>  
>  #include "regs/xe_gt_regs.h"
>  #include "xe_bb.h"
> @@ -500,6 +501,19 @@ static int do_gt_restart(struct xe_gt *gt)
>  	return 0;
>  }
>  
> +static void xe_uevent_gt_reset_failure(struct pci_dev *pdev, u8 id)
> +{
> +	char *reset_event[4];
> +
> +	reset_event[0] = XE_RESET_FAILED_UEVENT "=NEEDS_RESET";
> +	reset_event[1] = "RESET_FAILED=gt";
> +	reset_event[2] = kasprintf(GFP_KERNEL, "RESET_ID=%d", id);

should we also put which tile this is coming from?
Matt?

> +	reset_event[3] = NULL;
> +	kobject_uevent_env(&pdev->dev.kobj, KOBJ_CHANGE, reset_event);

Himal, could you please paste here an example of the output of this event
when monitoring it with the:
$ udevadm monitor
?

> +
> +	kfree(reset_event[2]);
> +}
> +
>  static int gt_reset(struct xe_gt *gt)
>  {
>  	int err;
> @@ -550,6 +564,9 @@ static int gt_reset(struct xe_gt *gt)
>  	xe_device_mem_access_put(gt_to_xe(gt));
>  	xe_gt_err(gt, "reset failed (%pe)\n", ERR_PTR(err));
>  
> +	/* Notify userspace about gt reset failure */
> +	xe_uevent_gt_reset_failure(to_pci_dev(gt_to_xe(gt)->drm.dev), gt->info.id);
> +
>  	return err;
>  }
>  
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index 347351a8f618..fdacee0a27c5 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -16,6 +16,14 @@ extern "C" {
>   * subject to backwards-compatibility constraints.
>   */
>  
> +/*
> + * Uevent generated by xe on it's pci node.
> + *
> + * XE_RESET_FAILED_UEVENT - Event is generated when attempt to reset engine
> + * fails. The value supplied with the event is always "NEEDS_RESET".
> + */
> +#define XE_RESET_FAILED_UEVENT "DEVICE_STATUS"
> +
>  /**
>   * struct xe_user_extension - Base class for defining a chain of extensions
>   *
> -- 
> 2.25.1
> 

  reply	other threads:[~2023-07-26 14:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-25 15:51 [Intel-xe] [PATCH v8 0/3] Notify userspace about uevent failure Himal Prasad Ghimiray
2023-07-25 15:51 ` [Intel-xe] [PATCH v8 1/3] fault-inject: Include linux/types.h by default Himal Prasad Ghimiray
2023-07-25 15:51 ` [Intel-xe] [PATCH v8 2/3] drm/xe: Notify Userspace when gt reset fails Himal Prasad Ghimiray
2023-07-26 14:39   ` Rodrigo Vivi [this message]
2023-07-26 17:14     ` Ghimiray, Himal Prasad
2023-07-26 18:33       ` Rodrigo Vivi
2023-07-25 15:51 ` [Intel-xe] [PATCH v8 3/3] drm/xe: Introduce fault injection for gt reset Himal Prasad Ghimiray
2023-07-25 16:38 ` [Intel-xe] ✓ CI.Patch_applied: success for Notify userspace about uevent failure Patchwork
2023-07-25 16:38 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-07-25 16:40 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-07-25 16:43 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-07-25 16:44 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-07-25 16:45 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-07-25 17:13 ` [Intel-xe] ○ CI.BAT: info " 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=ZMEwG8O9dZ8Ri7Kc@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=himal.prasad.ghimiray@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