From: "Christian König" <christian.koenig@amd.com>
To: Shuai Xue <xueshuai@linux.alibaba.com>,
alexander.deucher@amd.com, Xinhui.Pan@amd.com, airlied@gmail.com,
simona@ffwll.ch, lijo.lazar@amd.com, le.ma@amd.com,
hamza.mahfooz@amd.com, tzimmermann@suse.de, shaoyun.liu@amd.com,
Jun.Ma2@amd.com
Cc: amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Enable runtime modification of gpu_recovery parameter with validation
Date: Sun, 29 Dec 2024 21:11:38 +0100 [thread overview]
Message-ID: <563b1797-5524-44c5-89b0-754f245e6b8f@amd.com> (raw)
In-Reply-To: <20241228063245.61874-1-xueshuai@linux.alibaba.com>
Am 28.12.24 um 07:32 schrieb Shuai Xue:
> It's observed that most GPU jobs utilize less than one server, typically
> with each GPU being used by an independent job. If a job consumed poisoned
> data, a SIGBUS signal will be sent to terminate it. Meanwhile, the
> gpu_recovery parameter is set to -1 by default, the amdgpu driver resets
> all GPUs on the server. As a result, all jobs are terminated. Setting
> gpu_recovery to 0 provides an opportunity to preemptively evacuate other
> jobs and subsequently manually reset all GPUs.
*BIG* NAK to this whole approach!
Setting gpu_recovery to 0 in a production environment is *NOT* supported
at all and should never be done.
This is a pure debugging feature for JTAG debugging and can result in
random crashes and/or compromised data.
Please don't tell me that you tried to use this in a production environment.
Regards,
Christian.
> However, this parameter is
> read-only, necessitating correct settings at driver load. And reloading the
> GPU driver in a production environment can be challenging due to reference
> counts maintained by various monitoring services.
>
> Set the gpu_recovery parameter with read-write permission to enable runtime
> modification. It will enables users to dynamically manage GPU recovery
> mechanisms based on real-time requirements or conditions.
>
> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c | 26 ++++++++++++++++++++++++-
> 1 file changed, 25 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> index 38686203bea6..03dd902e1cec 100644
> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_drv.c
> @@ -563,12 +563,36 @@ module_param_named(lbpw, amdgpu_lbpw, int, 0444);
> MODULE_PARM_DESC(compute_multipipe, "Force compute queues to be spread across pipes (1 = enable, 0 = disable, -1 = auto)");
> module_param_named(compute_multipipe, amdgpu_compute_multipipe, int, 0444);
>
> +static int amdgpu_set_gpu_recovery(const char *buf,
> + const struct kernel_param *kp)
> +{
> + unsigned long val;
> + int ret;
> +
> + ret = kstrtol(buf, 10, &val);
> + if (ret < 0)
> + return ret;
> +
> + if (val != 1 && val != 0 && val != -1) {
> + pr_err("Invalid value for gpu_recovery: %ld, excepted 0,1,-1\n",
> + val);
> + return -EINVAL;
> + }
> +
> + return param_set_int(buf, kp);
> +}
> +
> +static const struct kernel_param_ops amdgpu_gpu_recovery_ops = {
> + .set = amdgpu_set_gpu_recovery,
> + .get = param_get_int,
> +};
> +
> /**
> * DOC: gpu_recovery (int)
> * Set to enable GPU recovery mechanism (1 = enable, 0 = disable). The default is -1 (auto, disabled except SRIOV).
> */
> MODULE_PARM_DESC(gpu_recovery, "Enable GPU recovery mechanism, (1 = enable, 0 = disable, -1 = auto)");
> -module_param_named(gpu_recovery, amdgpu_gpu_recovery, int, 0444);
> +module_param_cb(gpu_recovery, &amdgpu_gpu_recovery_ops, &amdgpu_gpu_recovery, 0644);
>
> /**
> * DOC: emu_mode (int)
next prev parent reply other threads:[~2024-12-29 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-28 6:32 Shuai Xue
2024-12-29 20:11 ` Christian König [this message]
2024-12-30 8:50 ` Shuai Xue
2025-01-03 8:21 ` AW: " Koenig, Christian
2025-01-06 12:09 ` Simona Vetter
2025-01-07 12:36 ` Christian König
2025-01-07 7:06 ` AW: " Shuai Xue
2025-01-07 12:34 ` Christian König
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=563b1797-5524-44c5-89b0-754f245e6b8f@amd.com \
--to=christian.koenig@amd.com \
--cc=Jun.Ma2@amd.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hamza.mahfooz@amd.com \
--cc=le.ma@amd.com \
--cc=lijo.lazar@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shaoyun.liu@amd.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=xueshuai@linux.alibaba.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
all inboxes | Powered by JetHome®