All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fangzhi Zuo <Jerry.Zuo@amd.com>
To: <igt-dev@lists.freedesktop.org>, <harry.wentland@amd.com>,
	<Christian.Koenig@amd.com>, <Alex.Hung@amd.com>
Cc: Fangzhi Zuo <Jerry.Zuo@amd.com>,
	Mark Broadworth <Mark.Broadworth@amd.com>
Subject: [PATCH 3/3] lib/igt_amd: Fix 8k Memory Allocation
Date: Wed, 17 Jun 2026 15:24:49 -0400	[thread overview]
Message-ID: <20260617192449.4166-3-Jerry.Zuo@amd.com> (raw)
In-Reply-To: <20260617192449.4166-1-Jerry.Zuo@amd.com>

For the memory allocation greater than 5k on small BAR system,
need to stop accessing BO with CPU.

Signed-off-by: Fangzhi Zuo <Jerry.Zuo@amd.com>
Tested-by: Mark Broadworth <Mark.Broadworth@amd.com>
---
 lib/igt_amd.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lib/igt_amd.c b/lib/igt_amd.c
index 47e587e54..5e8626c02 100644
--- a/lib/igt_amd.c
+++ b/lib/igt_amd.c
@@ -58,7 +58,7 @@ uint32_t igt_amd_create_bo(int fd, uint64_t size)
 	create.in.bo_size = size;
 	create.in.alignment = 256;
 	create.in.domains = AMDGPU_GEM_DOMAIN_VRAM;
-	create.in.domain_flags = AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED
+	create.in.domain_flags = AMDGPU_GEM_CREATE_NO_CPU_ACCESS
 				 | AMDGPU_GEM_CREATE_VRAM_CLEARED;
 
 	do_ioctl(fd, DRM_IOCTL_AMDGPU_GEM_CREATE, &create);
-- 
2.43.0


  parent reply	other threads:[~2026-06-17 19:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-17 19:24 [PATCH 1/3] tests/amdgpu: Add FRL Test Support Fangzhi Zuo
2026-06-17 19:24 ` [PATCH 2/3] tests/amdgpu: Fix for HDMI Compliance Automation Fangzhi Zuo
2026-06-17 19:24 ` Fangzhi Zuo [this message]
2026-06-17 20:56 ` ✓ Xe.CI.BAT: success for series starting with [1/3] tests/amdgpu: Add FRL Test Support Patchwork
2026-06-17 21:43 ` ✓ i915.CI.BAT: " 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=20260617192449.4166-3-Jerry.Zuo@amd.com \
    --to=jerry.zuo@amd.com \
    --cc=Alex.Hung@amd.com \
    --cc=Christian.Koenig@amd.com \
    --cc=Mark.Broadworth@amd.com \
    --cc=harry.wentland@amd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.