Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: vitaly prosyak <vprosyak@amd.com>
To: Tim Huang <tim.huang@amd.com>, igt-dev@lists.freedesktop.org
Cc: vitaly.prosyak@amd.com, alexander.deucher@amd.com, jie1zhan@amd.com
Subject: Re: [PATCH i-g-t] tests/amdgpu: fix secure bounce test failure on APUs
Date: Wed, 14 Aug 2024 22:12:45 -0400	[thread overview]
Message-ID: <77e2d206-4306-4f89-a418-62a7d4ea84f5@amd.com> (raw)
In-Reply-To: <20240815020147.155078-1-tim.huang@amd.com>

The changed looks good to me.

Reviewed-by: Vitaly Prosyak <vitaly.prosyak@amd.com>

On 2024-08-14 22:01, Tim Huang wrote:
> Some APUs have address tweak secure mechanisms that encrypt
> destination data preventing it from matching the original data.
>
> Rework the test case to ensure compatibility with these APUs.
>
> Signed-off-by: Tim Huang <tim.huang@amd.com>
> ---
>  tests/amdgpu/amd_security.c | 28 ++++++----------------------
>  1 file changed, 6 insertions(+), 22 deletions(-)
>
> diff --git a/tests/amdgpu/amd_security.c b/tests/amdgpu/amd_security.c
> index ec6883d3d..024cadc05 100644
> --- a/tests/amdgpu/amd_security.c
> +++ b/tests/amdgpu/amd_security.c
> @@ -147,8 +147,6 @@ amdgpu_bo_move(amdgpu_device_handle device, int fd,
>   */
>  static const uint8_t secure_pattern[] = { 0x5A, 0xFE, 0x05, 0xEC };
>  
> -static const uint8_t secure_pattern2[] = { 0xDE, 0xAD, 0xBE, 0xEF };
> -
>  static void
>  amdgpu_secure_bounce(amdgpu_device_handle device_handle, int fd,
>  		struct drm_amdgpu_info_hw_ip  *sdma_info,
> @@ -209,27 +207,13 @@ amdgpu_secure_bounce(amdgpu_device_handle device_handle, int fd,
>  	amdgpu_bo_lcopy(device_handle, ring_context, ip_block, SECURE_BUFFER_SIZE,
>  			secure == true ? 1 : 0);
>  
> -	/* Verify the contents of Bob. */
> -	for (pp = (__typeof__(pp))ring_context->bo2_cpu;
> -	     pp < (__typeof__(pp)) ring_context->bo2_cpu + SECURE_BUFFER_SIZE;
> -	     pp += sizeof(secure_pattern)) {
> -		r = memcmp(pp, secure_pattern, sizeof(secure_pattern));
> -		if (r) {
> -			// test failure
> -			igt_assert(false);
> -			break;
> -		}
> -	}
> -	/* Fill Bob with a pattern2 */
> -	for (pp = (__typeof__(pp))ring_context->bo2_cpu;
> -		pp < (__typeof__(pp)) ring_context->bo2_cpu + SECURE_BUFFER_SIZE;
> -		pp += sizeof(secure_pattern2))
> -		memcpy(pp, secure_pattern2, sizeof(secure_pattern2));
> -
>  	/* Move Bob to the GTT domain. */
>  	amdgpu_bo_move(device_handle, fd, ring_context, ip_block,
>  			AMDGPU_GEM_DOMAIN_GTT, 0);
>  
> +	/* Clean Alice first before do the copy from bob. */
> +	memset((void *)ring_context->bo_cpu, 0, SECURE_BUFFER_SIZE);
> +
>  	/* sDMA TMZ copy from Bob to Alice.
>  	 * bo is a source ,bo2 is destination
>  	 */
> @@ -250,11 +234,11 @@ amdgpu_secure_bounce(amdgpu_device_handle device_handle, int fd,
>  	amdgpu_bo_lcopy(device_handle, ring_context, ip_block, SECURE_BUFFER_SIZE,
>  			secure == true ? 1 : 0);
>  
> -	/* Verify the content of Alice if it matches to pattern2*/
> +	/* Verify the content of Alice if it matches to pattern */
>  	for (pp = (__typeof__(pp))ring_context->bo_cpu;
>  	     pp < (__typeof__(pp)) ring_context->bo_cpu + SECURE_BUFFER_SIZE;
> -	     pp += sizeof(secure_pattern2)) {
> -		r = memcmp(pp, secure_pattern2, sizeof(secure_pattern2));
> +	     pp += sizeof(secure_pattern)) {
> +		r = memcmp(pp, secure_pattern, sizeof(secure_pattern));
>  		if (r) {
>  			// test failure
>  			igt_assert(false);

  reply	other threads:[~2024-08-15  2:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-15  2:01 [PATCH i-g-t] tests/amdgpu: fix secure bounce test failure on APUs Tim Huang
2024-08-15  2:12 ` vitaly prosyak [this message]
2024-08-15  2:40 ` ✓ CI.xeBAT: success for " Patchwork
2024-08-15  2:50 ` ✓ Fi.CI.BAT: " Patchwork
2024-08-15  8:12 ` ✗ CI.xeFULL: failure " Patchwork
2024-08-16  6:05 ` ✗ 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=77e2d206-4306-4f89-a418-62a7d4ea84f5@amd.com \
    --to=vprosyak@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jie1zhan@amd.com \
    --cc=tim.huang@amd.com \
    --cc=vitaly.prosyak@amd.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