From: Matthew Auld <matthew.auld@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v10 11/15] lib/intel_allocator: treat default_alignment as the minimum
Date: Mon, 20 Nov 2023 18:24:26 +0000 [thread overview]
Message-ID: <20231120182430.88753-12-matthew.auld@intel.com> (raw)
In-Reply-To: <20231120182430.88753-1-matthew.auld@intel.com>
If something overrides the default alignment, we should only apply the
alignment if it is larger than the default_alignment.
v2 (Niranjana):
- Simplify slightly
v3:
- Also update the default-alignment testcase
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Cc: Pallavi Mishra <pallavi.mishra@intel.com>
Reviewed-by: Niranjana Vishwanathapura <niranjana.vishwanathapura@intel.com>
Reviewed-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
---
lib/intel_allocator.c | 4 ++--
tests/intel/api_intel_allocator.c | 8 ++++----
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/lib/intel_allocator.c b/lib/intel_allocator.c
index 01e025b46..341db2a50 100644
--- a/lib/intel_allocator.c
+++ b/lib/intel_allocator.c
@@ -584,8 +584,8 @@ static int handle_request(struct alloc_req *req, struct alloc_resp *resp)
break;
case REQ_ALLOC:
- if (!req->alloc.alignment)
- req->alloc.alignment = ial->default_alignment;
+ req->alloc.alignment = max(ial->default_alignment,
+ req->alloc.alignment);
resp->response_type = RESP_ALLOC;
resp->alloc.offset = ial->alloc(ial,
diff --git a/tests/intel/api_intel_allocator.c b/tests/intel/api_intel_allocator.c
index d19be3ce9..8e13a8808 100644
--- a/tests/intel/api_intel_allocator.c
+++ b/tests/intel/api_intel_allocator.c
@@ -206,7 +206,7 @@ static void reserve(int fd, uint8_t type)
static void default_alignment(int fd)
{
struct test_obj obj[3];
- uint64_t ahnd, default_alignment = 0x4000;
+ uint64_t ahnd, default_alignment = SZ_4K;
ahnd = intel_allocator_open_full(fd, 0, 0, 0, INTEL_ALLOCATOR_SIMPLE,
ALLOC_STRATEGY_LOW_TO_HIGH,
@@ -214,13 +214,13 @@ static void default_alignment(int fd)
for (int i = 0; i < ARRAY_SIZE(obj); i++) {
obj[i].handle = gem_handle_gen();
- obj[i].offset = intel_allocator_alloc(ahnd, obj[i].handle, 4096,
- i == 2 ? 4096 : 0);
+ obj[i].offset = intel_allocator_alloc(ahnd, obj[i].handle,
+ SZ_4K, i == 2 ? 0 : SZ_16K);
igt_debug("obj[%d].offset: %llx, handle: %u\n", i,
(long long) obj[i].offset, obj[i].handle);
}
- igt_assert_eq(obj[1].offset - obj[0].offset, default_alignment);
+ igt_assert_eq(obj[1].offset - obj[0].offset, SZ_16K);
/* obj[2] should be between obj[0] and obj[1] */
igt_assert(obj[0].offset < obj[2].offset);
igt_assert(obj[2].offset < obj[1].offset);
--
2.42.0
next prev parent reply other threads:[~2023-11-20 18:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 18:24 [igt-dev] [PATCH i-g-t v10 00/15] PAT and cache coherency support Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 01/15] drm-uapi/xe_drm: sync to get pat and coherency bits Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 02/15] lib/igt_fb: mark buffers as SCANOUT Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 03/15] lib/igt_draw: " Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 04/15] lib/xe: support explicit cpu_caching gem_create Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 05/15] tests/xe/mmap: add some tests for explicit cpu_caching Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 06/15] lib/intel_pat: add helpers for common pat_index modes Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 07/15] lib/allocator: add get_offset_pat_index() helper Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 08/15] lib/intel_blt: support pat_index Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 09/15] lib/intel_buf: " Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 10/15] lib/xe_ioctl: update vm_bind to account for pat_index Matthew Auld
2023-11-20 18:24 ` Matthew Auld [this message]
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 12/15] lib/intel_blt: tidy up alignment usage Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 13/15] lib/intel_batchbuffer: extend to include optional alignment Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 14/15] tests/xe: add some vm_bind pat_index tests Matthew Auld
2023-11-20 18:24 ` [igt-dev] [PATCH i-g-t v10 15/15] tests/intel-ci/xe: add pat and caching related tests Matthew Auld
2023-11-20 21:50 ` [igt-dev] ✗ Fi.CI.BAT: failure for PAT and cache coherency support (rev10) Patchwork
2023-11-20 23:14 ` [igt-dev] ✗ CI.xeBAT: " 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=20231120182430.88753-12-matthew.auld@intel.com \
--to=matthew.auld@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