public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Kamil Konieczny <kamil.konieczny@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Vivi@freedesktop.org,
	Alan Previn <alan.previn.teres.alexis@intel.com>,
	Rodrigo <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v1 1/1] tests/gem_pxp: Pre-MTL prep: PXP is now global.
Date: Tue, 6 Dec 2022 11:09:19 +0100	[thread overview]
Message-ID: <Y48Uz+Jy4cDCDFRs@kamilkon-desk1> (raw)
In-Reply-To: <20221206004856.145806-1-alan.previn.teres.alexis@intel.com>

Hi Alan,

don't put dot at end of commit message, e.g:
tests/gem_pxp: Pre-MTL prep: PXP is now global.
--------------------------------------------- ^

On 2022-12-05 at 16:48:56 -0800, Alan Previn wrote:
> From the PXP IGT, we assume PXP is a GT subsystem when we
> access then PXP debugfs to force a teardown for testiability.
> As part of kernel side PXP preparation work, the recent
> Intel GFX patchwork's series titled "drm/i915/pxp: Promote
> pxp subsystem to top-level of i915" has moved PXP to be a
> top level i915 subsystem. See kernel side rev9 URL at
> https://patchwork.freedesktop.org/patch/514043/?series=111650&rev=1).
-------------------------------------------------------------------- ^^
Please don't put any chars at end of http link.

> 
> To align with that, we need to change the debugfs path for pxp to
> ensure several of the substests (that rely on debugfs to simulate
> events that cannot be simulated by user-space) continue to work as
> expected.
> 
> NOTE: this patch should only be merged after the kernel side
> has merged.

You can remove this note, see below.

> 
> Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
> ---
>  tests/i915/gem_pxp.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/i915/gem_pxp.c b/tests/i915/gem_pxp.c
> index ffad9b5a..6cf254ca 100644
> --- a/tests/i915/gem_pxp.c
> +++ b/tests/i915/gem_pxp.c
> @@ -847,7 +847,7 @@ static void trigger_pxp_debugfs_forced_teardown(int i915)
>  	int fd, ret;
>  	char str[32];
>  
> -	fd = igt_debugfs_open(i915, "gt/pxp/terminate_state", O_RDWR);
> +	fd = igt_debugfs_open(i915, "pxp/terminate_state", O_RDWR);

You can make it work for both old and new with

	fd = igt_debugfs_open(i915, "pxp/terminate_state", O_RDWR); /* global pxp */
	if (fd == -1)
		fd = igt_debugfs_open(i915, "gt/pxp/terminate_state", O_RDWR);

and delete old one after some time.

Regards,
Kamil

>  	igt_assert_f(fd >= 0, "Can't open pxp termination debugfs\n");
>  	ret = snprintf(str, sizeof(str), "0x1");
>  	igt_assert(ret > 2 && ret < sizeof(str));
> 
> base-commit: c001793d5f22deb01918b6ba52af829794582df1
> -- 
> 2.34.1
> 

      parent reply	other threads:[~2022-12-06 10:09 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  0:48 [igt-dev] [PATCH i-g-t v1 1/1] tests/gem_pxp: Pre-MTL prep: PXP is now global Alan Previn
2022-12-06  1:32 ` Dixit, Ashutosh
2022-12-06  1:33 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,v1,1/1] " Patchwork
2022-12-06  3:36 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2022-12-06 10:09 ` Kamil Konieczny [this message]

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=Y48Uz+Jy4cDCDFRs@kamilkon-desk1 \
    --to=kamil.konieczny@linux.intel.com \
    --cc=Vivi@freedesktop.org \
    --cc=alan.previn.teres.alexis@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@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