Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Roper <matthew.d.roper@intel.com>
To: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 2/6] lib/igt_gt: Document fd argument in igt_open_forcewake_handle()
Date: Fri, 20 Sep 2024 10:15:14 -0700	[thread overview]
Message-ID: <20240920171514.GN5774@mdroper-desk1.amr.corp.intel.com> (raw)
In-Reply-To: <20240918163629.1186314-3-lucas.demarchi@intel.com>

On Wed, Sep 18, 2024 at 09:36:25AM -0700, Lucas De Marchi wrote:
> Document the fd argument to make it clear what -1 means, which is
> usually not the desired behavior.
> 
> Signed-off-by: Lucas De Marchi <lucas.demarchi@intel.com>
> ---
>  lib/igt_gt.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/lib/igt_gt.c b/lib/igt_gt.c
> index b043e2d41..d831d2448 100644
> --- a/lib/igt_gt.c
> +++ b/lib/igt_gt.c
> @@ -492,6 +492,7 @@ void igt_stop_hang_helper(void)
>  
>  /**
>   * igt_open_forcewake_handle:
> + * @fd: open i915 or xe drm file descriptor or -1 to use the first device found

Is it actually "first found" or is it just literally device 0 (which may
not even exist anymore)?  It looks like if -1 gets passed down to
igt_debugfs_path as the 'device' parameter, we just do a memset of the
stat structure to zero it, wind up setting idx = minor(0), and then use
the resulting idx (which should be 0) in the debugfs pathname.  Am I
missing something?

It looks like there are a few places in IGT passing -1 to debugfs
functions like this.  Maybe we should add a #define for it with a more
descriptive name to igt_debugfs.h?


Matt

>   *
>   * This functions opens the debugfs forcewake file and so prevents the GT from
>   * suspending. The reference is automatically dropped when the is closed.
> -- 
> 2.46.1
> 

-- 
Matt Roper
Graphics Software Engineer
Linux GPU Platform Enablement
Intel Corporation

  reply	other threads:[~2024-09-20 17:15 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18 16:36 [PATCH i-g-t 0/6] Add forcewake support for xe Lucas De Marchi
2024-09-18 16:36 ` [PATCH i-g-t 1/6] lib/igt_gt: Fix forcewake open Lucas De Marchi
2024-09-20 16:58   ` Matt Roper
2024-09-18 16:36 ` [PATCH i-g-t 2/6] lib/igt_gt: Document fd argument in igt_open_forcewake_handle() Lucas De Marchi
2024-09-20 17:15   ` Matt Roper [this message]
2024-09-20 20:20     ` Lucas De Marchi
2024-09-18 16:36 ` [PATCH i-g-t 3/6] lib/igt_gt: Make igt_open_forcewake_handle() xe-compatible Lucas De Marchi
2024-09-20 17:17   ` Matt Roper
2024-09-18 16:36 ` [PATCH i-g-t 4/6] lib/igt_gt: Fallback on filenames in igt_open_forcewake_handle() Lucas De Marchi
2024-09-18 19:16   ` [PATCH i-g-t v1.1] " Lucas De Marchi
2024-09-20 17:27     ` Matt Roper
2024-09-18 16:36 ` [PATCH i-g-t 5/6] tools/intel_reg: Add wrapper for reg access init Lucas De Marchi
2024-09-20 17:35   ` Matt Roper
2024-09-18 16:36 ` [PATCH i-g-t 6/6] tools/intel_reg: Add forcewake support to xe Lucas De Marchi
2024-09-20 17:43   ` Ville Syrjälä
2024-09-20 18:01   ` Matt Roper
2024-09-20 18:04     ` Matt Roper
2024-09-20 18:30       ` Ville Syrjälä
2024-09-20 19:43         ` Lucas De Marchi
2024-09-18 17:47 ` ✓ CI.xeBAT: success for Add forcewake support for xe Patchwork
2024-09-18 17:48 ` ✗ Fi.CI.BAT: failure " Patchwork
2024-09-18 19:42 ` ✓ CI.xeBAT: success for Add forcewake support for xe (rev2) Patchwork
2024-09-18 19:54 ` ✓ Fi.CI.BAT: " Patchwork
2024-09-19  3:57 ` ✗ CI.xeFULL: failure for Add forcewake support for xe Patchwork
2024-09-19  6:06 ` ✗ CI.xeFULL: failure for Add forcewake support for xe (rev2) Patchwork
2024-09-19  7:27 ` ✗ Fi.CI.IGT: " 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=20240920171514.GN5774@mdroper-desk1.amr.corp.intel.com \
    --to=matthew.d.roper@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=lucas.demarchi@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