From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: <linux-kernel@vger.kernel.org>, <intel-xe@lists.freedesktop.org>,
"Jonathan Cavitt" <jonathan.cavitt@intel.com>
Subject: Re: [PATCH v5 2/2] drm/xe: Increase devcoredump timeout
Date: Mon, 10 Jun 2024 16:17:34 -0400 [thread overview]
Message-ID: <ZmdfXmPKE177-Rfo@intel.com> (raw)
In-Reply-To: <20240610161133.156566-2-jose.souza@intel.com>
On Mon, Jun 10, 2024 at 09:11:33AM -0700, José Roberto de Souza wrote:
> 5 minutes is too short for a regular user to search and understand
> what he needs to do to report capture devcoredump and report a bug to
> us, so here increasing this timeout to 1 hour.
>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Cc: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Acked-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
> Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> ---
> drivers/gpu/drm/xe/xe_devcoredump.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_devcoredump.c b/drivers/gpu/drm/xe/xe_devcoredump.c
> index d7f2d19a77c10..62c2b10fbf1d2 100644
> --- a/drivers/gpu/drm/xe/xe_devcoredump.c
> +++ b/drivers/gpu/drm/xe/xe_devcoredump.c
> @@ -53,6 +53,9 @@
>
> #ifdef CONFIG_DEV_COREDUMP
>
> +/* 1 hour timeout */
> +#define XE_COREDUMP_TIMEOUT_JIFFIES (60 * 60 * HZ)
o.O! 1h?!
we should likely already add a config option for that.
but anyway, let's move with that and adjust as we go.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> +
> static struct xe_device *coredump_to_xe(const struct xe_devcoredump *coredump)
> {
> return container_of(coredump, struct xe_device, devcoredump);
> @@ -247,8 +250,9 @@ void xe_devcoredump(struct xe_sched_job *job)
> drm_info(&xe->drm, "Check your /sys/class/drm/card%d/device/devcoredump/data\n",
> xe->drm.primary->index);
>
> - dev_coredumpm(xe->drm.dev, THIS_MODULE, coredump, 0, GFP_KERNEL,
> - xe_devcoredump_read, xe_devcoredump_free);
> + dev_coredumpm_timeout(xe->drm.dev, THIS_MODULE, coredump, 0, GFP_KERNEL,
> + xe_devcoredump_read, xe_devcoredump_free,
> + XE_COREDUMP_TIMEOUT_JIFFIES);
> }
>
> static void xe_driver_devcoredump_fini(void *arg)
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-06-10 20:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 16:11 [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout() José Roberto de Souza
2024-06-10 16:11 ` [PATCH v5 2/2] drm/xe: Increase devcoredump timeout José Roberto de Souza
2024-06-10 20:17 ` Rodrigo Vivi [this message]
2024-06-10 16:38 ` ✓ CI.Patch_applied: success for series starting with [v5,1/2] devcoredump: Add dev_coredumpm_timeout() Patchwork
2024-06-10 16:38 ` ✓ CI.checkpatch: " Patchwork
2024-06-10 16:39 ` ✓ CI.KUnit: " Patchwork
2024-06-10 16:51 ` ✓ CI.Build: " Patchwork
2024-06-10 16:53 ` ✓ CI.Hooks: " Patchwork
2024-06-10 16:54 ` ✓ CI.checksparse: " Patchwork
2024-06-10 20:16 ` [PATCH v5 1/2] " Rodrigo Vivi
2024-06-10 20:42 ` Cavitt, Jonathan
2024-06-10 20:52 ` Souza, Jose
2024-06-10 22:00 ` Rodrigo Vivi
2024-06-11 6:19 ` kernel test robot
2024-06-11 7:12 ` ✓ CI.Patch_applied: success for series starting with [v5,1/2] devcoredump: Add dev_coredumpm_timeout() (rev2) Patchwork
2024-06-11 7:12 ` ✓ CI.checkpatch: " Patchwork
2024-06-11 7:13 ` ✓ CI.KUnit: " Patchwork
2024-06-11 7:25 ` ✓ CI.Build: " Patchwork
2024-06-11 7:27 ` ✗ CI.Hooks: failure " Patchwork
2024-06-11 7:29 ` ✓ CI.checksparse: success " Patchwork
2024-06-11 7:51 ` ✓ CI.BAT: " Patchwork
2024-06-11 10:31 ` ✗ CI.FULL: failure " Patchwork
2024-06-11 10:37 ` [PATCH v5 1/2] devcoredump: Add dev_coredumpm_timeout() kernel test robot
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=ZmdfXmPKE177-Rfo@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.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 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.