From: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t v2 1/4] lib/intel_blt: Release an offset in the allocator on buffer destroy
Date: Fri, 13 Oct 2023 13:28:45 +0200 [thread overview]
Message-ID: <20231013112848.68164-2-zbigniew.kempczynski@intel.com> (raw)
In-Reply-To: <20231013112848.68164-1-zbigniew.kempczynski@intel.com>
Blitter library code requires allocator handle only at the execution
time. That means blt_copy_object structure is allocator agnostic and
offsets are taken for block-copy or fast-copy just before operation.
Operations on bo's like close/create requires to reflect on the
allocator state, otherwise allocator will contain outdated
offsets + sizes leading to fail on allocator operations or the exec.
Helpers blt_create_object() and blt_destroy_object() are unaware
of allocator so if in the meantime object was used in block-copy or
fast-copy it has assigned offset in the allocator. Destroying object
with blt_destroy_object() doesn't release this offset what might
cause failures described above.
There're two possibilities how to solve this - to couple blitter
library with allocator or provide additional helpers which will
release offset in the allocator on destroy path. Latter one is
easier to provide so this is a subject of this change.
Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
Cc: Karolina Stolarek <karolina.stolarek@intel.com>
Reviewed-by: Karolina Stolarek <karolina.stolarek@intel.com>
---
lib/intel_blt.c | 15 ++++++++++++++-
lib/intel_blt.h | 2 ++
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/lib/intel_blt.c b/lib/intel_blt.c
index a76c7a4045..3c5e97963d 100644
--- a/lib/intel_blt.c
+++ b/lib/intel_blt.c
@@ -1635,15 +1635,28 @@ blt_create_object(const struct blt_copy_data *blt, uint32_t region,
return obj;
}
-void blt_destroy_object(int fd, struct blt_copy_object *obj)
+static void __blt_destroy_object(int fd, uint64_t ahnd, struct blt_copy_object *obj)
{
if (obj->ptr)
munmap(obj->ptr, obj->size);
gem_close(fd, obj->handle);
+ if (ahnd)
+ intel_allocator_free(ahnd, obj->handle);
free(obj);
}
+void blt_destroy_object(int fd, struct blt_copy_object *obj)
+{
+ __blt_destroy_object(fd, 0, obj);
+}
+
+void blt_destroy_object_and_alloc_free(int fd, uint64_t ahnd,
+ struct blt_copy_object *obj)
+{
+ __blt_destroy_object(fd, ahnd, obj);
+}
+
void blt_set_object(struct blt_copy_object *obj,
uint32_t handle, uint64_t size, uint32_t region,
uint8_t mocs_index, enum blt_tiling_type tiling,
diff --git a/lib/intel_blt.h b/lib/intel_blt.h
index 7b4271620a..657e51dd57 100644
--- a/lib/intel_blt.h
+++ b/lib/intel_blt.h
@@ -245,6 +245,8 @@ blt_create_object(const struct blt_copy_data *blt, uint32_t region,
enum blt_compression_type compression_type,
bool create_mapping);
void blt_destroy_object(int fd, struct blt_copy_object *obj);
+void blt_destroy_object_and_alloc_free(int fd, uint64_t ahnd,
+ struct blt_copy_object *obj);
void blt_set_object(struct blt_copy_object *obj,
uint32_t handle, uint64_t size, uint32_t region,
uint8_t mocs_index, enum blt_tiling_type tiling,
--
2.34.1
next prev parent reply other threads:[~2023-10-13 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 11:28 [igt-dev] [PATCH i-g-t v2 0/4] Add flat-ccs tests Zbigniew Kempczyński
2023-10-13 11:28 ` Zbigniew Kempczyński [this message]
2023-10-13 11:28 ` [igt-dev] [PATCH i-g-t v2 2/4] lib/igt_sizes: Add common SZ_* header Zbigniew Kempczyński
2023-10-17 10:58 ` Kamil Konieczny
2023-10-18 7:24 ` Zbigniew Kempczyński
2023-10-13 11:28 ` [igt-dev] [PATCH i-g-t v2 3/4] tests/xe_evict_ccs: Add evict ccs test Zbigniew Kempczyński
2023-10-17 15:28 ` Matthew Auld
2023-10-18 17:37 ` Zbigniew Kempczyński
2023-10-13 11:28 ` [igt-dev] [PATCH i-g-t v2 4/4] intel-ci/xe-fast-feedback: Add two xe_evict_ccs subtests for Xe run Zbigniew Kempczyński
2023-10-13 17:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for Add flat-ccs tests (rev2) Patchwork
2023-10-13 18:22 ` [igt-dev] ✓ CI.xeBAT: success " 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=20231013112848.68164-2-zbigniew.kempczynski@intel.com \
--to=zbigniew.kempczynski@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