From: Adam Miszczak <adam.miszczak@linux.intel.com>
To: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [i-g-t] tests/core_hotunplug: Be more specific on sysfs vs. debugfs issues
Date: Tue, 23 Mar 2021 10:13:05 +0100 [thread overview]
Message-ID: <20210323101305.00002148@linux.intel.com> (raw)
In-Reply-To: <20210318120554.961342-1-janusz.krzysztofik@linux.intel.com>
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com> wrote:
> Messages displayed on sysfs health check failures don't provide
> information which subtree of sysfs actually failed - device sysfs
> itself or device debugfs. That information could make debugging more
> easy if available.
>
> Be more specific when reporting sysfs health check failures.
>
> Signed-off-by: Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>
> ---
> tests/core_hotunplug.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/tests/core_hotunplug.c b/tests/core_hotunplug.c
> index e7d2a4472..56a88fefd 100644
> --- a/tests/core_hotunplug.c
> +++ b/tests/core_hotunplug.c
> @@ -351,11 +351,13 @@ static void node_healthcheck(struct hotunplug *priv, unsigned flags)
> if (!priv->failure) {
> char path[200];
>
> - priv->failure = "Device sysfs healthckeck failure!";
> local_debug("%s\n", "running device sysfs healthcheck");
> - if (igt_sysfs_path(fd_drm, path, sizeof(path)) &&
> - igt_debugfs_path(fd_drm, path, sizeof(path)))
> - priv->failure = NULL;
> + priv->failure = "Device sysfs healthckeck failure!";
> + if (igt_sysfs_path(fd_drm, path, sizeof(path))) {
> + priv->failure = "Device debugfs healthckeck failure!";
> + if (igt_debugfs_path(fd_drm, path, sizeof(path)))
> + priv->failure = NULL;
> + }
> }
>
> fd_drm = close_device(fd_drm, "", "health checked ");
LGTM,
Reviewed-by: Adam Miszczak <adam.miszczak@linux.intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2021-03-23 9:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 12:05 [igt-dev] [PATCH i-g-t] tests/core_hotunplug: Be more specific on sysfs vs. debugfs issues Janusz Krzysztofik
2021-03-18 13:03 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-03-18 15:41 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-03-23 10:02 ` Janusz Krzysztofik
2021-03-23 17:48 ` Vudum, Lakshminarayana
2021-03-23 9:13 ` Adam Miszczak [this message]
2021-03-23 10:31 ` [igt-dev] [i-g-t] " Janusz Krzysztofik
2021-03-23 17:31 ` [igt-dev] ✓ Fi.CI.IGT: success for " 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=20210323101305.00002148@linux.intel.com \
--to=adam.miszczak@linux.intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox