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>
Subject: Re: [PATCH i-g-t v3 5/7] tests/intel/xe_pxp: Test PXP submissions
Date: Thu, 13 Feb 2025 22:47:00 +0000 [thread overview]
Message-ID: <52fca5c57e86ed5f18f0489b643be3e0b8ef54d2.camel@intel.com> (raw)
In-Reply-To: <20250213003904.2059770-6-daniele.ceraolospurio@intel.com>
looks good.
Reviewed-by: Alan Previn <alan.previn.teres.alexis@intel.com>
On Wed, 2025-02-12 at 16:38 -0800, Ceraolo Spurio, Daniele wrote:
> The render supports PXP usage via rendercopy. We can use this to test
> that a user is able to correctly encrypt their data. In particular, we
> cover these 2 scenarios:
>
> 1) copy from clear to encrypted - we expect the dest buffer to not match
> the src one due to the encryption.
>
> 2) copy from encrypted to encrypted = we expect the 2 BOs to match since
> they hold the same data encrypted with the same key.
>
> Note that the clear to clear copy is already covered by the
> xe_render_copy test, while encrypted to clear is obviously not a
> supported case.
>
> Since the render_copy uses the intel_batchbuffer helpers, those helpers
> have been updated to support vm bind of protected objects.
>
> v2: move igt_require calls inside the subtest
> v3: Better comments for rsvd1 overload, rename variables for clarity,
> updated commit msg.
>
> Signed-off-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Alan Previn <alan.previn.teres.alexis@intel.com>
> ---
> lib/intel_batchbuffer.c | 37 ++++--
alan:snip
next prev parent reply other threads:[~2025-02-13 22:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 0:38 [PATCH i-g-t v3 0/7] Xe: Add tests for PXP Daniele Ceraolo Spurio
2025-02-13 0:38 ` [PATCH i-g-t v3 1/7] drm-uapi/xe: Sync with PXP uapi updates Daniele Ceraolo Spurio
2025-02-13 22:38 ` Teres Alexis, Alan Previn
2025-02-13 0:38 ` [PATCH i-g-t v3 2/7] tests/intel/xe_vm: Update invalid flag subtest with valid PXP flag Daniele Ceraolo Spurio
2025-02-13 0:38 ` [PATCH i-g-t v3 3/7] tests/intel/xe_query: Add test for PXP status query Daniele Ceraolo Spurio
2025-02-13 0:38 ` [PATCH i-g-t v3 4/7] tests/intel/xe_pxp: Add PXP object and queue creation tests Daniele Ceraolo Spurio
2025-02-13 0:38 ` [PATCH i-g-t v3 5/7] tests/intel/xe_pxp: Test PXP submissions Daniele Ceraolo Spurio
2025-02-13 22:47 ` Teres Alexis, Alan Previn [this message]
2025-02-13 0:39 ` [PATCH i-g-t v3 6/7] tests/intel/xe_pxp: Termination tests Daniele Ceraolo Spurio
2025-02-13 23:30 ` Teres Alexis, Alan Previn
2025-02-14 20:07 ` Kamil Konieczny
2025-02-21 0:44 ` Daniele Ceraolo Spurio
2025-02-13 0:39 ` [PATCH i-g-t v3 7/7] tests/intel/xe_pxp: Test encrypted FBs Daniele Ceraolo Spurio
2025-02-13 2:58 ` ✗ GitLab.Pipeline: warning for Xe: Add tests for PXP (rev3) 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=52fca5c57e86ed5f18f0489b643be3e0b8ef54d2.camel@intel.com \
--to=alan.previn.teres.alexis@intel.com \
--cc=daniele.ceraolospurio@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