From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Andi Shyti <andi.shyti@linux.intel.com>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Tvrtko Ursulin <tursulin@ursulin.net>,
Chris Wilson <chris.p.wilson@linux.intel.com>
Subject: Re: [PATCH] drm/i915/gt: Continue creating engine sysfs files even after a failure
Date: Tue, 20 Aug 2024 17:22:40 -0400 [thread overview]
Message-ID: <ZsUJIFVKuIX_pbDw@intel.com> (raw)
In-Reply-To: <20240819113140.325235-1-andi.shyti@linux.intel.com>
On Mon, Aug 19, 2024 at 01:31:40PM +0200, Andi Shyti wrote:
> The i915 driver generates sysfs entries for each engine of the
> GPU in /sys/class/drm/cardX/engines/.
>
> The process is straightforward: we loop over the UABI engines and
> for each one, we:
>
> - Create the object.
> - Create basic files.
> - If the engine supports timeslicing, create timeslice duration files.
> - If the engine supports preemption, create preemption-related files.
> - Create default value files.
>
> Currently, if any of these steps fail, the process stops, and no
> further sysfs files are created.
>
> However, it's not necessary to stop the process on failure.
> Instead, we can continue creating the remaining sysfs files for
> the other engines. Even if some files fail to be created, the
> list of engines can still be retrieved by querying i915.
>
> Signed-off-by: Andi Shyti <andi.shyti@linux.intel.com>
> ---
> Hi,
>
> It might make sense to create an "inv-<engine_name>" if something
> goes wrong, so that the user is aware that the engine exists, but
> the sysfs file is not present.
well, if the sysfs dir/files creation is failing, then it will
probably be unreliable anyway right?
>
> One further improvement would be to provide more information
> about thei failure reason the dev_warn() message.
So, perhaps this patch should already go there and remove
the dev_err and add individual dev_warn for each failing path?
Also it looks something is off with the goto paths...
That if (0) is also ugly... probably better to use a
kobject_put with continue on every failing point as well...
>
> Andi
>
> drivers/gpu/drm/i915/gt/sysfs_engines.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/sysfs_engines.c b/drivers/gpu/drm/i915/gt/sysfs_engines.c
> index 021f51d9b456..aab2759067d2 100644
> --- a/drivers/gpu/drm/i915/gt/sysfs_engines.c
> +++ b/drivers/gpu/drm/i915/gt/sysfs_engines.c
> @@ -530,9 +530,8 @@ void intel_engines_add_sysfs(struct drm_i915_private *i915)
> err_object:
> kobject_put(kobj);
> err_engine:
> - dev_err(kdev, "Failed to add sysfs engine '%s'\n",
> - engine->name);
> - break;
> + dev_warn(kdev, "Failed to add sysfs engine '%s'\n",
> + engine->name);
> }
> }
> }
> --
> 2.45.2
>
next prev parent reply other threads:[~2024-08-20 21:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 11:31 [PATCH] drm/i915/gt: Continue creating engine sysfs files even after a failure Andi Shyti
2024-08-20 21:22 ` Rodrigo Vivi [this message]
2024-08-21 7:32 ` Andi Shyti
2024-08-21 10:34 ` Andi Shyti
2024-08-23 13:41 ` Rodrigo Vivi
2024-08-23 22:26 ` Andi Shyti
2024-08-27 17:05 ` Daniel Vetter
2024-08-28 20:17 ` Rodrigo Vivi
2024-09-04 13:20 ` Andi Shyti
2024-09-04 14:34 ` Jani Nikula
2024-09-04 15:08 ` Tvrtko Ursulin
2024-09-04 15:13 ` Rodrigo Vivi
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=ZsUJIFVKuIX_pbDw@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=chris.p.wilson@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=tursulin@ursulin.net \
/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;
as well as URLs for NNTP newsgroup(s).