From: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
To: Francois Dugast <francois.dugast@intel.com>,
intel-xe@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/xe/uapi: Remove reset uevent for now
Date: Fri, 15 Dec 2023 15:45:45 +0530 [thread overview]
Message-ID: <c35a24b1-dee6-4e73-9d1b-970e43e9a700@linux.intel.com> (raw)
In-Reply-To: <20231215094329.7-1-francois.dugast@intel.com>
On 12/15/23 15:13, Francois Dugast wrote:
> From: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> This kernel uevent is getting removed for now. It will come
> back later with a better future proof name.
>
> v2: Rebase (Francois Dugast)
as mentioned in IGT series we need to drop this commit as well
14a663d83da2 drm/xe: Introduce fault injection for gt reset.
Thanks,
Aravind.
>
> Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Cc: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
> Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
> drivers/gpu/drm/xe/xe_gt.c | 18 ------------------
> include/uapi/drm/xe_drm.h | 11 -----------
> 2 files changed, 29 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_gt.c b/drivers/gpu/drm/xe/xe_gt.c
> index f5d18e98f8b6..3af2adec1295 100644
> --- a/drivers/gpu/drm/xe/xe_gt.c
> +++ b/drivers/gpu/drm/xe/xe_gt.c
> @@ -589,20 +589,6 @@ static int do_gt_restart(struct xe_gt *gt)
> return 0;
> }
>
> -static void xe_uevent_gt_reset_failure(struct pci_dev *pdev, u8 tile_id, u8 gt_id)
> -{
> - char *reset_event[4];
> -
> - reset_event[0] = DRM_XE_RESET_FAILED_UEVENT "=NEEDS_RESET";
> - reset_event[1] = kasprintf(GFP_KERNEL, "TILE_ID=%d", tile_id);
> - reset_event[2] = kasprintf(GFP_KERNEL, "GT_ID=%d", gt_id);
> - reset_event[3] = NULL;
> - kobject_uevent_env(&pdev->dev.kobj, KOBJ_CHANGE, reset_event);
> -
> - kfree(reset_event[1]);
> - kfree(reset_event[2]);
> -}
> -
> static int gt_reset(struct xe_gt *gt)
> {
> int err;
> @@ -659,10 +645,6 @@ static int gt_reset(struct xe_gt *gt)
> err_fail:
> 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_to_tile(gt)->id, gt->info.id);
> -
> gt_to_xe(gt)->needs_flr_on_fini = true;
>
> return err;
> diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> index b905ab16aa40..8c35ec43faef 100644
> --- a/include/uapi/drm/xe_drm.h
> +++ b/include/uapi/drm/xe_drm.h
> @@ -20,7 +20,6 @@ extern "C" {
> * 2. Extension definition and helper structs
> * 3. IOCTL's Query structs in the order of the Query's entries.
> * 4. The rest of IOCTL structs in the order of IOCTL declaration.
> - * 5. uEvents
> */
>
> /**
> @@ -1341,16 +1340,6 @@ struct drm_xe_wait_user_fence {
> __u64 reserved[2];
> };
>
> -/**
> - * DOC: uevent generated by xe on it's pci node.
> - *
> - * DRM_XE_RESET_FAILED_UEVENT - Event is generated when attempt to reset gt
> - * fails. The value supplied with the event is always "NEEDS_RESET".
> - * Additional information supplied is tile id and gt id of the gt unit for
> - * which reset has failed.
> - */
> -#define DRM_XE_RESET_FAILED_UEVENT "DEVICE_STATUS"
> -
> #if defined(__cplusplus)
> }
> #endif
next prev parent reply other threads:[~2023-12-15 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 9:43 [PATCH] drm/xe/uapi: Remove reset uevent for now Francois Dugast
2023-12-15 9:57 ` ✗ CI.Patch_applied: failure for " Patchwork
2023-12-15 10:15 ` Aravind Iddamsetty [this message]
2023-12-15 12:38 ` [PATCH] " Rodrigo Vivi
[not found] <20231215004351.1520696-1-rodrigo.vivi@intel.com>
[not found] ` <MW4PR11MB7056E2099198099CC15AA2A6B393A@MW4PR11MB7056.namprd11.prod.outlook.com>
2023-12-15 14:59 ` Francois Dugast
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=c35a24b1-dee6-4e73-9d1b-970e43e9a700@linux.intel.com \
--to=aravind.iddamsetty@linux.intel.com \
--cc=francois.dugast@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.