Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Teres Alexis, Alan Previn" <alan.previn.teres.alexis@intel.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
	"Ceraolo Spurio, Daniele" <daniele.ceraolospurio@intel.com>
Cc: "kamil.konieczny@linux.intel.com" <kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH i-g-t v5 5/6] tests/intel/xe_pxp: Termination tests
Date: Fri, 7 Mar 2025 01:04:19 +0000	[thread overview]
Message-ID: <462500b98da99d4bb73a00ad2131089db2226221.camel@intel.com> (raw)
In-Reply-To: <20250305233951.3488609-6-daniele.ceraolospurio@intel.com>

I see you have added the documentation for existing __xe_bb_exec and xe_exec_sync,
as well as the new xe_exec_sync_failable. Also, u have included <fcntl.h> to address
the undeclared ‘O_RDONLY’. These addresses the earlier comments from Kamil.

I also notice you have added the drmModeResPtr usage to disable all of the
display connectors before running the runtime-pm subtest via setup_rpm()
(and re-enabling after via restore_rpm) since an active display pipeline
could prevent the runtime-pm from kicking in. Good catch on this one.

It would be better to get Kamil's take on whether this version of patch #5 meets
the requests he had about fixtures in v3 especially which the updated changes...
also I am not 100% clear on the usage of fixture WRT zero-impact-of-subtest-enumeration
vs cleanup-after-subtest-assert.

That said, I'll provide an RB here (since Kamil didnt raise it again in V4) and we can
check with him offline:

Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>


On Wed, 2025-03-05 at 15:39 -0800, Ceraolo Spurio, Daniele wrote:
> 
alan:snip




  reply	other threads:[~2025-03-07  1:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05 23:39 [PATCH i-g-t v5 0/6] Xe: Add tests for PXP Daniele Ceraolo Spurio
2025-03-05 23:39 ` [PATCH i-g-t v5 1/6] tests/intel/xe_vm: Update invalid flag subtest with valid PXP flag Daniele Ceraolo Spurio
2025-03-05 23:39 ` [PATCH i-g-t v5 2/6] tests/intel/xe_query: Add test for PXP status query Daniele Ceraolo Spurio
2025-03-06 21:33   ` [PATCH i-g-t] " Daniele Ceraolo Spurio
2025-03-06 22:54     ` Teres Alexis, Alan Previn
2025-03-05 23:39 ` [PATCH i-g-t v5 3/6] tests/intel/xe_pxp: Add PXP object and queue creation tests Daniele Ceraolo Spurio
2025-03-05 23:39 ` [PATCH i-g-t v5 4/6] tests/intel/xe_pxp: Test PXP submissions Daniele Ceraolo Spurio
2025-03-05 23:39 ` [PATCH i-g-t v5 5/6] tests/intel/xe_pxp: Termination tests Daniele Ceraolo Spurio
2025-03-07  1:04   ` Teres Alexis, Alan Previn [this message]
2025-03-05 23:39 ` [PATCH i-g-t v5 6/6] tests/intel/xe_pxp: Test encrypted FBs Daniele Ceraolo Spurio
2025-03-06  8:21 ` ✓ Xe.CI.BAT: success for Xe: Add tests for PXP (rev5) Patchwork
2025-03-06  8:43 ` ✓ i915.CI.BAT: " Patchwork
2025-03-06 11:29 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-06 16:18 ` ✗ Xe.CI.Full: " Patchwork
2025-03-07  7:42 ` ✓ Xe.CI.BAT: success for Xe: Add tests for PXP (rev6) Patchwork
2025-03-07  8:03 ` ✓ i915.CI.BAT: " Patchwork
2025-03-07  9:39 ` ✗ i915.CI.Full: failure " Patchwork
2025-03-07 22:15 ` ✗ 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=462500b98da99d4bb73a00ad2131089db2226221.camel@intel.com \
    --to=alan.previn.teres.alexis@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@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