From: Francois Dugast <francois.dugast@intel.com>
To: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
Cc: igt-dev@lists.freedesktop.org,
"Michał Wajdeczko" <michal.wajdeczko@intel.com>
Subject: Re: [PATCH i-g-t 1/4] lib/igt_sysfs: Add support for device unbinding
Date: Tue, 18 Feb 2025 13:19:39 +0100 [thread overview]
Message-ID: <Z7R629psykoNL1bt@fdugast-desk> (raw)
In-Reply-To: <20250207072902.12582-2-satyanarayana.k.v.p@intel.com>
On Fri, Feb 07, 2025 at 12:58:59PM +0530, Satyanarayana K V P wrote:
> It does not harm anything when we try to unbind a device which
> is already unbinded. We do not want to throw assertion when
> the device is already unbinded.
>
> Signed-off-by: Satyanarayana K V P <satyanarayana.k.v.p@intel.com>
> Cc: Michał Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
Reviewed-by: Francois Dugast <francois.dugast@intel.com>
> ---
> lib/igt_sysfs.c | 4 ++++
> lib/igt_sysfs.h | 1 +
> 2 files changed, 5 insertions(+)
>
> diff --git a/lib/igt_sysfs.c b/lib/igt_sysfs.c
> index 2e4c2ee63..3fffaf96b 100644
> --- a/lib/igt_sysfs.c
> +++ b/lib/igt_sysfs.c
> @@ -1509,6 +1509,10 @@ int xe_sysfs_driver_do(int xe_device, char pci_slot[], enum xe_sysfs_driver_acti
> igt_assert(igt_sysfs_set(sysfs, "unbind", pci_slot));
> close(sysfs);
> break;
> + case XE_SYSFS_DRIVER_TRY_UNBIND:
> + igt_sysfs_set(sysfs, "unbind", pci_slot);
> + close(sysfs);
> + break;
> case XE_SYSFS_DRIVER_REBIND:
> igt_assert(igt_sysfs_set(sysfs, "unbind", pci_slot));
>
> diff --git a/lib/igt_sysfs.h b/lib/igt_sysfs.h
> index 86345f3d1..cc4971e70 100644
> --- a/lib/igt_sysfs.h
> +++ b/lib/igt_sysfs.h
> @@ -187,6 +187,7 @@ enum xe_sysfs_driver_action {
> XE_SYSFS_DRIVER_BIND,
> XE_SYSFS_DRIVER_TRY_BIND,
> XE_SYSFS_DRIVER_UNBIND,
> + XE_SYSFS_DRIVER_TRY_UNBIND,
> XE_SYSFS_DRIVER_REBIND,
> };
>
> --
> 2.35.3
>
next prev parent reply other threads:[~2025-02-18 12:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 7:28 [PATCH i-g-t 0/4] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv() xe_guc_mmio_send_recv() Satyanarayana K V P
2025-02-07 7:28 ` [PATCH i-g-t 1/4] lib/igt_sysfs: Add support for device unbinding Satyanarayana K V P
2025-02-18 12:19 ` Francois Dugast [this message]
2025-02-07 7:29 ` [PATCH i-g-t 2/4] tests/intel/xe_fault_injection: Make setup_injection_fault() programmable Satyanarayana K V P
2025-02-18 12:46 ` Francois Dugast
2025-02-07 7:29 ` [PATCH i-g-t 3/4] tests/intel/xe_fault_injection: Add helper functions to inject fault with specific budget parameter Satyanarayana K V P
2025-02-18 13:04 ` Francois Dugast
2025-02-07 7:29 ` [PATCH i-g-t 4/4] tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv & xe_guc_mmio_send_recv Satyanarayana K V P
2025-02-18 13:48 ` Francois Dugast
2025-02-18 14:06 ` Michal Wajdeczko
2025-02-18 16:40 ` Francois Dugast
2025-02-08 0:01 ` ✓ i915.CI.BAT: success for tests/intel/xe_fault_injection: Inject errors during xe_guc_ct_send_recv() xe_guc_mmio_send_recv() Patchwork
2025-02-08 0:42 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-08 15:59 ` ✗ i915.CI.Full: failure " Patchwork
2025-02-08 17:21 ` ✗ Xe.CI.Full: " 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=Z7R629psykoNL1bt@fdugast-desk \
--to=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
--cc=satyanarayana.k.v.p@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