From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Francois Dugast <francois.dugast@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 3/5] tests/intel/xe_fault_injection: Use igt_sysfs helpers
Date: Fri, 8 Nov 2024 14:18:25 -0500 [thread overview]
Message-ID: <Zy5kAfpglK9dWMYO@intel.com> (raw)
In-Reply-To: <20241108160021.1202234-4-francois.dugast@intel.com>
On Fri, Nov 08, 2024 at 04:59:31PM +0100, Francois Dugast wrote:
> Make use of existing helpers from igt_sysfs where possible. This
> improves robustness and removes code duplication.
>
> Signed-off-by: Francois Dugast <francois.dugast@intel.com>
> ---
> tests/intel/xe_fault_injection.c | 127 +++++++++++++++----------------
> 1 file changed, 61 insertions(+), 66 deletions(-)
>
> diff --git a/tests/intel/xe_fault_injection.c b/tests/intel/xe_fault_injection.c
> index 891b4d70b..87e567a54 100644
> --- a/tests/intel/xe_fault_injection.c
> +++ b/tests/intel/xe_fault_injection.c
> @@ -11,15 +11,13 @@
> * Test category: fault injection
> */
>
> +#include <limits.h>
> +
> #include "igt.h"
> #include "igt_device.h"
> #include "igt_kmod.h"
> #include "igt_sysfs.h"
>
> -#define MAX_LINE_SIZE 1024
> -#define PATH_FUNCTIONS_INJECTABLE "/sys/kernel/debug/fail_function/injectable"
> -#define PATH_FUNCTIONS_INJECT "/sys/kernel/debug/fail_function/inject"
> -#define PATH_FUNCTIONS_RETVAL "/sys/kernel/debug/fail_function/%s/retval"
> #define INJECT_ERRNO -ENOMEM
>
> enum injection_list_action {
> @@ -27,40 +25,66 @@ enum injection_list_action {
> INJECTION_LIST_REMOVE,
> };
>
> +static int fail_function_open(void)
> +{
> + int debugfs_fail_function_dir_fd;
> + const char *debugfs_root;
> + char path[96];
> +
> + debugfs_root = igt_debugfs_mount();
> + igt_assert(debugfs_root);
> +
> + sprintf(path, "%s/fail_function", debugfs_root);
> +
> + if (access(path, F_OK))
> + return -1;
> +
> + debugfs_fail_function_dir_fd = open(path, O_RDONLY);
> + igt_debug_on_f(debugfs_fail_function_dir_fd < 0, "path: %s\n", path);
> +
> + return debugfs_fail_function_dir_fd;
> +}
> +
> /*
> * The injectable file requires CONFIG_FUNCTION_ERROR_INJECTION in kernel.
> */
> -static bool function_error_injection_enabled(void)
> +static bool fail_function_injection_enabled(void)
> {
> - FILE *file = fopen(PATH_FUNCTIONS_INJECTABLE, "rw");
> + char *contents;
> + int dir;
>
> - if (file) {
> - fclose(file);
> - return true;
> - }
> + dir = fail_function_open();
> + if (dir < 0)
> + return false;
> +
> + contents = igt_sysfs_get(dir, "injectable");
> + if (contents == NULL)
> + return false;
> +
> + free(contents);
>
> - return false;
> + return true;
> }
>
> static void injection_list_do(enum injection_list_action action, const char function_name[])
> {
> - FILE *file_inject;
> + int dir;
>
> - file_inject = fopen(PATH_FUNCTIONS_INJECT, "w");
> - igt_assert(file_inject);
> + dir = fail_function_open();
> + igt_assert_lte(0, dir);
>
> switch(action) {
> case INJECTION_LIST_ADD:
> - fprintf(file_inject, "%s", function_name);
> + igt_assert_lte(0, igt_sysfs_printf(dir, "inject", "%s", function_name));
> break;
> case INJECTION_LIST_REMOVE:
> - fprintf(file_inject, "!%s", function_name);
> + igt_assert_lte(0, igt_sysfs_printf(dir, "inject", "!%s", function_name));
> break;
> default:
> igt_assert(!"missing");
> }
>
> - fclose(file_inject);
> + close(dir);
> }
>
> /*
> @@ -68,61 +92,33 @@ static void injection_list_do(enum injection_list_action action, const char func
> */
> static void setup_injection_fault(void)
> {
> - FILE *file;
> -
> - file = fopen("/sys/kernel/debug/fail_function/task-filter", "w");
> - igt_assert(file);
> - fprintf(file, "N");
> - fclose(file);
> -
> - file = fopen("/sys/kernel/debug/fail_function/probability", "w");
> - igt_assert(file);
> - fprintf(file, "100");
> - fclose(file);
> -
> - file = fopen("/sys/kernel/debug/fail_function/interval", "w");
> - igt_assert(file);
> - fprintf(file, "0");
> - fclose(file);
> -
> - file = fopen("/sys/kernel/debug/fail_function/times", "w");
> - igt_assert(file);
> - fprintf(file, "-1");
> - fclose(file);
> -
> - file = fopen("/sys/kernel/debug/fail_function/space", "w");
> - igt_assert(file);
> - fprintf(file, "0");
> - fclose(file);
> -
> - file = fopen("/sys/kernel/debug/fail_function/verbose", "w");
> - igt_assert(file);
> - fprintf(file, "1");
> - fclose(file);
> -}
> + int dir;
>
> -static void cleanup_injection_fault(void)
> -{
> - FILE *file;
> + dir = fail_function_open();
> + igt_assert_lte(0, dir);
> +
> + igt_assert_lte(0, igt_sysfs_printf(dir, "task-filter", "N"));
> + igt_sysfs_set_u32(dir, "probability", 100);
> + igt_sysfs_set_u32(dir, "interval", 0);
> + igt_sysfs_set_s32(dir, "times", -1);
> + igt_sysfs_set_u32(dir, "space", 0);
> + igt_sysfs_set_u32(dir, "verbose", 0);
is verbose changing from 1 to 0 intentional? wouldn't it deserve a
separate patch?
>
> - file = fopen(PATH_FUNCTIONS_INJECT, "w");
> - igt_assert(file);
> - fprintf(file, "\n");
> - fclose(file);
> + close(dir);
> }
>
> static void set_retval(const char function_name[], long long retval)
> {
> - FILE *file_retval;
> - char file_path[MAX_LINE_SIZE];
> + char path[96];
> + int dir;
>
> - sprintf(file_path, PATH_FUNCTIONS_RETVAL, function_name);
> + dir = fail_function_open();
> + igt_assert_lte(0, dir);
>
> - file_retval = fopen(file_path, "w");
> - igt_assert(file_retval);
> + sprintf(path, "%s/retval", function_name);
> + igt_assert_lte(0, igt_sysfs_printf(dir, path, "%#016llx", retval));
>
> - fprintf(file_retval, "%#016llx", retval);
> - fclose(file_retval);
> + close(dir);
> }
>
> /**
> @@ -161,7 +157,7 @@ inject_fault_probe(int fd, char pci_slot[], const char function_name[])
> igt_main
> {
> int fd;
> - char pci_slot[MAX_LINE_SIZE];
> + char pci_slot[NAME_MAX];
> const struct section {
> const char *name;
> } probe_function_sections[] = {
> @@ -182,7 +178,7 @@ igt_main
> };
>
> igt_fixture {
> - igt_require(function_error_injection_enabled());
> + igt_require(fail_function_injection_enabled());
> fd = drm_open_driver(DRIVER_XE);
> igt_device_get_pci_slot_name(fd, pci_slot);
> setup_injection_fault();
> @@ -194,7 +190,6 @@ igt_main
> inject_fault_probe(fd, pci_slot, s->name);
>
> igt_fixture {
> - cleanup_injection_fault();
> drm_close_driver(fd);
> xe_sysfs_driver_do(fd, pci_slot, XE_SYSFS_DRIVER_BIND);
> }
> --
> 2.43.0
>
next prev parent reply other threads:[~2024-11-08 19:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 15:59 [PATCH i-g-t 0/5] xe_fault_injection improvements Francois Dugast
2024-11-08 15:59 ` [PATCH i-g-t 1/5] tests/intel/xe_fault_injection: Use a static list of functions Francois Dugast
2024-11-08 19:09 ` Rodrigo Vivi
2024-11-08 15:59 ` [PATCH i-g-t 2/5] lib/igt_sysfs: Add igt_sysfs_{get,set}_s32 Francois Dugast
2024-11-08 15:59 ` [PATCH i-g-t 3/5] tests/intel/xe_fault_injection: Use igt_sysfs helpers Francois Dugast
2024-11-08 19:18 ` Rodrigo Vivi [this message]
2024-11-08 15:59 ` [PATCH i-g-t 4/5] tests/intel/xe_fault_injection: Inject errors during vm create IOCTL Francois Dugast
2024-11-08 20:10 ` Rodrigo Vivi
2024-11-08 15:59 ` [PATCH i-g-t 5/5] tests/intel/xe_fault_injection: Inject errors during vm bind IOCTL Francois Dugast
2024-11-08 20:10 ` Rodrigo Vivi
2024-11-08 17:09 ` ✗ Fi.CI.BAT: failure for xe_fault_injection improvements (rev2) Patchwork
2024-11-08 17:14 ` ✗ CI.xeBAT: " Patchwork
2024-11-09 19:11 ` ✗ CI.xeFULL: " 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=Zy5kAfpglK9dWMYO@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox