* [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
@ 2023-01-07 15:15 Arunpravin Paneer Selvam
2023-01-07 16:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
` (3 more replies)
0 siblings, 4 replies; 8+ messages in thread
From: Arunpravin Paneer Selvam @ 2023-01-07 15:15 UTC (permalink / raw)
To: dri-devel, intel-gfx, amd-gfx, matthew.auld, christian.koenig,
alexander.deucher
Cc: Arunpravin Paneer Selvam
As we are observing low numbers in viewperf graphics benchmark, we
are strictly not allowing the top down flag enabled allocations
to steal the memory space from cpu visible region.
The approach is, we are sorting each order list entries in
ascending order and compare the last entry of each order
list in the freelist and return the max block.
This patch improves the viewperf 3D benchmark scores.
Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
---
drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
1 file changed, 54 insertions(+), 27 deletions(-)
diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
index 11bb59399471..50916b2f2fc5 100644
--- a/drivers/gpu/drm/drm_buddy.c
+++ b/drivers/gpu/drm/drm_buddy.c
@@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
kmem_cache_free(slab_blocks, block);
}
+static void list_insert_sorted(struct drm_buddy *mm,
+ struct drm_buddy_block *block)
+{
+ struct drm_buddy_block *node;
+ struct list_head *head;
+
+ head = &mm->free_list[drm_buddy_block_order(block)];
+ if (list_empty(head)) {
+ list_add(&block->link, head);
+ return;
+ }
+
+ list_for_each_entry(node, head, link)
+ if (drm_buddy_block_offset(block) < drm_buddy_block_offset(node))
+ break;
+
+ __list_add(&block->link, node->link.prev, &node->link);
+}
+
static void mark_allocated(struct drm_buddy_block *block)
{
block->header &= ~DRM_BUDDY_HEADER_STATE;
@@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
block->header &= ~DRM_BUDDY_HEADER_STATE;
block->header |= DRM_BUDDY_FREE;
- list_add(&block->link,
- &mm->free_list[drm_buddy_block_order(block)]);
+ list_insert_sorted(mm, block);
}
static void mark_split(struct drm_buddy_block *block)
@@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
}
static struct drm_buddy_block *
-get_maxblock(struct list_head *head)
+get_maxblock(struct drm_buddy *mm, unsigned int order)
{
struct drm_buddy_block *max_block = NULL, *node;
+ unsigned int i;
- max_block = list_first_entry_or_null(head,
- struct drm_buddy_block,
- link);
- if (!max_block)
- return NULL;
+ for (i = order; i <= mm->max_order; ++i) {
+ if (!list_empty(&mm->free_list[i])) {
+ node = list_last_entry(&mm->free_list[i],
+ struct drm_buddy_block,
+ link);
+ if (!max_block) {
+ max_block = node;
+ continue;
+ }
- list_for_each_entry(node, head, link) {
- if (drm_buddy_block_offset(node) >
- drm_buddy_block_offset(max_block))
- max_block = node;
+ if (drm_buddy_block_offset(node) >
+ drm_buddy_block_offset(max_block)) {
+ max_block = node;
+ }
+ }
}
return max_block;
@@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
unsigned long flags)
{
struct drm_buddy_block *block = NULL;
- unsigned int i;
+ unsigned int tmp;
int err;
- for (i = order; i <= mm->max_order; ++i) {
- if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
- block = get_maxblock(&mm->free_list[i]);
- if (block)
- break;
- } else {
- block = list_first_entry_or_null(&mm->free_list[i],
- struct drm_buddy_block,
- link);
- if (block)
- break;
+ if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
+ block = get_maxblock(mm, order);
+ if (block)
+ /* Store the obtained block order */
+ tmp = drm_buddy_block_order(block);
+ } else {
+ for (tmp = order; tmp <= mm->max_order; ++tmp) {
+ if (!list_empty(&mm->free_list[tmp])) {
+ block = list_last_entry(&mm->free_list[tmp],
+ struct drm_buddy_block,
+ link);
+ if (block)
+ break;
+ }
}
}
@@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
BUG_ON(!drm_buddy_block_is_free(block));
- while (i != order) {
+ while (tmp != order) {
err = split_block(mm, block);
if (unlikely(err))
goto err_undo;
block = block->right;
- i--;
+ tmp--;
}
return block;
err_undo:
- if (i != order)
+ if (tmp != order)
__drm_buddy_free(mm, block);
return ERR_PTR(err);
}
--
2.25.1
^ permalink raw reply related [flat|nested] 8+ messages in thread
* [Intel-gfx] ✓ Fi.CI.BAT: success for drm: Alloc high address for drm buddy topdown flag
2023-01-07 15:15 [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag Arunpravin Paneer Selvam
@ 2023-01-07 16:08 ` Patchwork
2023-01-07 17:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
` (2 subsequent siblings)
3 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2023-01-07 16:08 UTC (permalink / raw)
To: Arunpravin Paneer Selvam; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 5236 bytes --]
== Series Details ==
Series: drm: Alloc high address for drm buddy topdown flag
URL : https://patchwork.freedesktop.org/series/112502/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_12554 -> Patchwork_112502v1
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/index.html
Participating hosts (42 -> 40)
------------------------------
Missing (2): bat-atsm-1 fi-snb-2520m
Known issues
------------
Here are the changes found in Patchwork_112502v1 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@i915_selftest@live@execlists:
- fi-bsw-n3050: [PASS][1] -> [INCOMPLETE][2] ([i915#6972])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-bsw-n3050/igt@i915_selftest@live@execlists.html
* igt@i915_selftest@live@gt_heartbeat:
- fi-apl-guc: [PASS][3] -> [DMESG-FAIL][4] ([i915#5334])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-apl-guc/igt@i915_selftest@live@gt_heartbeat.html
- fi-kbl-soraka: [PASS][5] -> [DMESG-FAIL][6] ([i915#5334])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-kbl-soraka/igt@i915_selftest@live@gt_heartbeat.html
* igt@i915_selftest@live@workarounds:
- fi-rkl-guc: [PASS][7] -> [INCOMPLETE][8] ([i915#4983])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-rkl-guc/igt@i915_selftest@live@workarounds.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-rkl-guc/igt@i915_selftest@live@workarounds.html
* igt@runner@aborted:
- fi-bsw-n3050: NOTRUN -> [FAIL][9] ([fdo#109271] / [i915#4312])
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-bsw-n3050/igt@runner@aborted.html
#### Possible fixes ####
* igt@gem_exec_gttfill@basic:
- fi-pnv-d510: [FAIL][10] ([i915#7229]) -> [PASS][11]
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-pnv-d510/igt@gem_exec_gttfill@basic.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-pnv-d510/igt@gem_exec_gttfill@basic.html
* igt@i915_selftest@live@migrate:
- bat-adlp-4: [DMESG-FAIL][12] ([i915#7699]) -> [PASS][13]
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/bat-adlp-4/igt@i915_selftest@live@migrate.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/bat-adlp-4/igt@i915_selftest@live@migrate.html
* igt@i915_selftest@live@workarounds:
- {bat-adln-1}: [INCOMPLETE][14] ([i915#7467]) -> [PASS][15]
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/bat-adln-1/igt@i915_selftest@live@workarounds.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/bat-adln-1/igt@i915_selftest@live@workarounds.html
#### Warnings ####
* igt@i915_suspend@basic-s3-without-i915:
- fi-rkl-11600: [FAIL][16] ([fdo#103375]) -> [INCOMPLETE][17] ([i915#4817])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/fi-rkl-11600/igt@i915_suspend@basic-s3-without-i915.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109271]: https://bugs.freedesktop.org/show_bug.cgi?id=109271
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[i915#4312]: https://gitlab.freedesktop.org/drm/intel/issues/4312
[i915#4817]: https://gitlab.freedesktop.org/drm/intel/issues/4817
[i915#4983]: https://gitlab.freedesktop.org/drm/intel/issues/4983
[i915#5334]: https://gitlab.freedesktop.org/drm/intel/issues/5334
[i915#6972]: https://gitlab.freedesktop.org/drm/intel/issues/6972
[i915#6997]: https://gitlab.freedesktop.org/drm/intel/issues/6997
[i915#7229]: https://gitlab.freedesktop.org/drm/intel/issues/7229
[i915#7467]: https://gitlab.freedesktop.org/drm/intel/issues/7467
[i915#7699]: https://gitlab.freedesktop.org/drm/intel/issues/7699
Build changes
-------------
* Linux: CI_DRM_12554 -> Patchwork_112502v1
CI-20190529: 20190529
CI_DRM_12554: 77b21315725079a0f62117b62ab9e6fc3c5b325d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7110: db10a19b94d1d7ae5ba62eb48d52c47ccb27766f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_112502v1: 77b21315725079a0f62117b62ab9e6fc3c5b325d @ git://anongit.freedesktop.org/gfx-ci/linux
### Linux commits
ec23ecdc7e21 drm: Alloc high address for drm buddy topdown flag
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/index.html
[-- Attachment #2: Type: text/html, Size: 5986 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* [Intel-gfx] ✗ Fi.CI.IGT: failure for drm: Alloc high address for drm buddy topdown flag
2023-01-07 15:15 [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag Arunpravin Paneer Selvam
2023-01-07 16:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
@ 2023-01-07 17:30 ` Patchwork
2023-01-09 10:13 ` [Intel-gfx] [PATCH] " Christian König
2023-01-10 12:02 ` Matthew Auld
3 siblings, 0 replies; 8+ messages in thread
From: Patchwork @ 2023-01-07 17:30 UTC (permalink / raw)
To: Arunpravin Paneer Selvam; +Cc: intel-gfx
[-- Attachment #1: Type: text/plain, Size: 19942 bytes --]
== Series Details ==
Series: drm: Alloc high address for drm buddy topdown flag
URL : https://patchwork.freedesktop.org/series/112502/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_12554_full -> Patchwork_112502v1_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with Patchwork_112502v1_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in Patchwork_112502v1_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/index.html
Participating hosts (13 -> 11)
------------------------------
Additional (1): shard-rkl0
Missing (3): pig-skl-6260u pig-kbl-iris pig-glk-j5005
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in Patchwork_112502v1_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_flip@busy-flip@a-hdmi-a2:
- shard-glk: [PASS][1] -> [FAIL][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-glk4/igt@kms_flip@busy-flip@a-hdmi-a2.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-glk4/igt@kms_flip@busy-flip@a-hdmi-a2.html
Known issues
------------
Here are the changes found in Patchwork_112502v1_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_exec_fair@basic-pace-share@rcs0:
- shard-glk: [PASS][3] -> [FAIL][4] ([i915#2842])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-glk3/igt@gem_exec_fair@basic-pace-share@rcs0.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-glk8/igt@gem_exec_fair@basic-pace-share@rcs0.html
* igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size:
- shard-glk: [PASS][5] -> [FAIL][6] ([i915#2346]) +1 similar issue
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-glk9/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-glk3/igt@kms_cursor_legacy@flip-vs-cursor@atomic-transitions-varying-size.html
#### Possible fixes ####
* igt@drm_fdinfo@idle@rcs0:
- {shard-rkl}: [FAIL][7] ([i915#7742]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@drm_fdinfo@idle@rcs0.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-2/igt@drm_fdinfo@idle@rcs0.html
* igt@fbdev@nullptr:
- {shard-rkl}: [SKIP][9] ([i915#2582]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-5/igt@fbdev@nullptr.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@fbdev@nullptr.html
* igt@fbdev@pan:
- {shard-tglu}: [SKIP][11] ([i915#2582]) -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-tglu-6/igt@fbdev@pan.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-tglu-7/igt@fbdev@pan.html
* igt@gem_ctx_exec@basic-nohangcheck:
- {shard-rkl}: [FAIL][13] ([i915#6268]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-6/igt@gem_ctx_exec@basic-nohangcheck.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gem_ctx_exec@basic-nohangcheck.html
* igt@gem_eio@reset-stress:
- {shard-dg1}: [FAIL][15] ([i915#5784]) -> [PASS][16]
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-dg1-18/igt@gem_eio@reset-stress.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-dg1-19/igt@gem_eio@reset-stress.html
* igt@gem_eio@suspend:
- {shard-rkl}: [FAIL][17] ([i915#7052]) -> [PASS][18]
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-3/igt@gem_eio@suspend.html
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gem_eio@suspend.html
* igt@gem_exec_endless@dispatch@bcs0:
- {shard-rkl}: [SKIP][19] ([i915#6247]) -> [PASS][20]
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-5/igt@gem_exec_endless@dispatch@bcs0.html
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@gem_exec_endless@dispatch@bcs0.html
* igt@gem_exec_fair@basic-deadline:
- shard-glk: [FAIL][21] ([i915#2846]) -> [PASS][22]
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-glk4/igt@gem_exec_fair@basic-deadline.html
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-glk2/igt@gem_exec_fair@basic-deadline.html
* igt@gem_exec_fair@basic-none-share@rcs0:
- {shard-rkl}: [FAIL][23] ([i915#2842]) -> [PASS][24]
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@gem_exec_fair@basic-none-share@rcs0.html
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gem_exec_fair@basic-none-share@rcs0.html
* igt@gem_exec_reloc@basic-write-gtt:
- {shard-rkl}: [SKIP][25] ([i915#3281]) -> [PASS][26] +8 similar issues
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@gem_exec_reloc@basic-write-gtt.html
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gem_exec_reloc@basic-write-gtt.html
* igt@gem_set_tiling_vs_pwrite:
- {shard-rkl}: [SKIP][27] ([i915#3282]) -> [PASS][28] +5 similar issues
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@gem_set_tiling_vs_pwrite.html
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gem_set_tiling_vs_pwrite.html
* igt@gen9_exec_parse@shadow-peek:
- {shard-rkl}: [SKIP][29] ([i915#2527]) -> [PASS][30] +2 similar issues
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@gen9_exec_parse@shadow-peek.html
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@gen9_exec_parse@shadow-peek.html
* igt@i915_pipe_stress@stress-xrgb8888-ytiled:
- {shard-rkl}: [SKIP][31] ([i915#4098]) -> [PASS][32]
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-1/igt@i915_pipe_stress@stress-xrgb8888-ytiled.html
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@i915_pipe_stress@stress-xrgb8888-ytiled.html
* igt@i915_pm_dc@dc6-dpms:
- {shard-rkl}: [SKIP][33] ([i915#3361]) -> [PASS][34]
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-5/igt@i915_pm_dc@dc6-dpms.html
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@i915_pm_dc@dc6-dpms.html
* igt@i915_pm_rc6_residency@rc6-idle@vcs0:
- {shard-dg1}: [FAIL][35] ([i915#3591]) -> [PASS][36] +2 similar issues
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-dg1-17/igt@i915_pm_rc6_residency@rc6-idle@vcs0.html
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-dg1-17/igt@i915_pm_rc6_residency@rc6-idle@vcs0.html
* igt@i915_pm_rpm@dpms-non-lpsp:
- {shard-dg1}: [SKIP][37] ([i915#1397]) -> [PASS][38] +2 similar issues
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-dg1-14/igt@i915_pm_rpm@dpms-non-lpsp.html
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-dg1-17/igt@i915_pm_rpm@dpms-non-lpsp.html
* igt@i915_pm_rpm@fences-dpms:
- {shard-rkl}: [SKIP][39] ([i915#1849]) -> [PASS][40]
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-1/igt@i915_pm_rpm@fences-dpms.html
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@i915_pm_rpm@fences-dpms.html
* igt@i915_pm_sseu@full-enable:
- {shard-rkl}: [SKIP][41] ([i915#4387]) -> [PASS][42]
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-3/igt@i915_pm_sseu@full-enable.html
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@i915_pm_sseu@full-enable.html
* igt@kms_big_fb@x-tiled-addfb-size-offset-overflow:
- {shard-tglu}: [SKIP][43] ([i915#1845] / [i915#7651]) -> [PASS][44] +4 similar issues
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-tglu-6/igt@kms_big_fb@x-tiled-addfb-size-offset-overflow.html
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-tglu-7/igt@kms_big_fb@x-tiled-addfb-size-offset-overflow.html
* igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-180-async-flip:
- {shard-rkl}: [SKIP][45] ([i915#1845] / [i915#4098]) -> [PASS][46] +16 similar issues
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-2/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@kms_big_fb@x-tiled-max-hw-stride-32bpp-rotate-180-async-flip.html
* igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc:
- {shard-tglu}: [SKIP][47] ([i915#7651]) -> [PASS][48] +13 similar issues
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-tglu-6/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-tglu-2/igt@kms_ccs@pipe-c-random-ccs-data-y_tiled_gen12_rc_ccs_cc.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- {shard-rkl}: [SKIP][49] ([i915#1849] / [i915#4098]) -> [PASS][50] +10 similar issues
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-1/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_plane@pixel-format-source-clamping@pipe-b-planes:
- {shard-tglu}: [SKIP][51] ([i915#1849] / [i915#3558]) -> [PASS][52] +1 similar issue
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-tglu-6/igt@kms_plane@pixel-format-source-clamping@pipe-b-planes.html
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-tglu-7/igt@kms_plane@pixel-format-source-clamping@pipe-b-planes.html
* igt@kms_properties@crtc-properties-atomic:
- {shard-tglu}: [SKIP][53] ([i915#1849]) -> [PASS][54] +5 similar issues
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-tglu-6/igt@kms_properties@crtc-properties-atomic.html
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-tglu-2/igt@kms_properties@crtc-properties-atomic.html
* igt@kms_universal_plane@cursor-fb-leak-pipe-b:
- {shard-rkl}: [SKIP][55] ([i915#1845] / [i915#4070] / [i915#4098]) -> [PASS][56] +1 similar issue
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-1/igt@kms_universal_plane@cursor-fb-leak-pipe-b.html
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-6/igt@kms_universal_plane@cursor-fb-leak-pipe-b.html
* igt@perf@mi-rpc:
- {shard-rkl}: [SKIP][57] ([i915#2434]) -> [PASS][58]
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-6/igt@perf@mi-rpc.html
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@perf@mi-rpc.html
* igt@prime_vgem@basic-write:
- {shard-rkl}: [SKIP][59] ([fdo#109295] / [i915#3291] / [i915#3708]) -> [PASS][60]
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_12554/shard-rkl-4/igt@prime_vgem@basic-write.html
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/shard-rkl-5/igt@prime_vgem@basic-write.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#103375]: https://bugs.freedesktop.org/show_bug.cgi?id=103375
[fdo#109274]: https://bugs.freedesktop.org/show_bug.cgi?id=109274
[fdo#109280]: https://bugs.freedesktop.org/show_bug.cgi?id=109280
[fdo#109283]: https://bugs.freedesktop.org/show_bug.cgi?id=109283
[fdo#109289]: https://bugs.freedesktop.org/show_bug.cgi?id=109289
[fdo#109295]: https://bugs.freedesktop.org/show_bug.cgi?id=109295
[fdo#109315]: https://bugs.freedesktop.org/show_bug.cgi?id=109315
[fdo#110189]: https://bugs.freedesktop.org/show_bug.cgi?id=110189
[fdo#110723]: https://bugs.freedesktop.org/show_bug.cgi?id=110723
[fdo#111068]: https://bugs.freedesktop.org/show_bug.cgi?id=111068
[fdo#111614]: https://bugs.freedesktop.org/show_bug.cgi?id=111614
[fdo#111615]: https://bugs.freedesktop.org/show_bug.cgi?id=111615
[fdo#111644]: https://bugs.freedesktop.org/show_bug.cgi?id=111644
[fdo#111825]: https://bugs.freedesktop.org/show_bug.cgi?id=111825
[fdo#111827]: https://bugs.freedesktop.org/show_bug.cgi?id=111827
[fdo#112283]: https://bugs.freedesktop.org/show_bug.cgi?id=112283
[i915#1072]: https://gitlab.freedesktop.org/drm/intel/issues/1072
[i915#132]: https://gitlab.freedesktop.org/drm/intel/issues/132
[i915#1397]: https://gitlab.freedesktop.org/drm/intel/issues/1397
[i915#1755]: https://gitlab.freedesktop.org/drm/intel/issues/1755
[i915#1825]: https://gitlab.freedesktop.org/drm/intel/issues/1825
[i915#1839]: https://gitlab.freedesktop.org/drm/intel/issues/1839
[i915#1845]: https://gitlab.freedesktop.org/drm/intel/issues/1845
[i915#1849]: https://gitlab.freedesktop.org/drm/intel/issues/1849
[i915#1937]: https://gitlab.freedesktop.org/drm/intel/issues/1937
[i915#2232]: https://gitlab.freedesktop.org/drm/intel/issues/2232
[i915#2346]: https://gitlab.freedesktop.org/drm/intel/issues/2346
[i915#2434]: https://gitlab.freedesktop.org/drm/intel/issues/2434
[i915#2527]: https://gitlab.freedesktop.org/drm/intel/issues/2527
[i915#2532]: https://gitlab.freedesktop.org/drm/intel/issues/2532
[i915#2575]: https://gitlab.freedesktop.org/drm/intel/issues/2575
[i915#2582]: https://gitlab.freedesktop.org/drm/intel/issues/2582
[i915#2587]: https://gitlab.freedesktop.org/drm/intel/issues/2587
[i915#2658]: https://gitlab.freedesktop.org/drm/intel/issues/2658
[i915#2672]: https://gitlab.freedesktop.org/drm/intel/issues/2672
[i915#2681]: https://gitlab.freedesktop.org/drm/intel/issues/2681
[i915#2842]: https://gitlab.freedesktop.org/drm/intel/issues/2842
[i915#2846]: https://gitlab.freedesktop.org/drm/intel/issues/2846
[i915#2856]: https://gitlab.freedesktop.org/drm/intel/issues/2856
[i915#2920]: https://gitlab.freedesktop.org/drm/intel/issues/2920
[i915#2994]: https://gitlab.freedesktop.org/drm/intel/issues/2994
[i915#3116]: https://gitlab.freedesktop.org/drm/intel/issues/3116
[i915#3281]: https://gitlab.freedesktop.org/drm/intel/issues/3281
[i915#3282]: https://gitlab.freedesktop.org/drm/intel/issues/3282
[i915#3291]: https://gitlab.freedesktop.org/drm/intel/issues/3291
[i915#3297]: https://gitlab.freedesktop.org/drm/intel/issues/3297
[i915#3299]: https://gitlab.freedesktop.org/drm/intel/issues/3299
[i915#3359]: https://gitlab.freedesktop.org/drm/intel/issues/3359
[i915#3361]: https://gitlab.freedesktop.org/drm/intel/issues/3361
[i915#3469]: https://gitlab.freedesktop.org/drm/intel/issues/3469
[i915#3536]: https://gitlab.freedesktop.org/drm/intel/issues/3536
[i915#3546]: https://gitlab.freedesktop.org/drm/intel/issues/3546
[i915#3555]: https://gitlab.freedesktop.org/drm/intel/issues/3555
[i915#3558]: https://gitlab.freedesktop.org/drm/intel/issues/3558
[i915#3591]: https://gitlab.freedesktop.org/drm/intel/issues/3591
[i915#3637]: https://gitlab.freedesktop.org/drm/intel/issues/3637
[i915#3638]: https://gitlab.freedesktop.org/drm/intel/issues/3638
[i915#3689]: https://gitlab.freedesktop.org/drm/intel/issues/3689
[i915#3708]: https://gitlab.freedesktop.org/drm/intel/issues/3708
[i915#3734]: https://gitlab.freedesktop.org/drm/intel/issues/3734
[i915#3825]: https://gitlab.freedesktop.org/drm/intel/issues/3825
[i915#3886]: https://gitlab.freedesktop.org/drm/intel/issues/3886
[i915#404]: https://gitlab.freedesktop.org/drm/intel/issues/404
[i915#4070]: https://gitlab.freedesktop.org/drm/intel/issues/4070
[i915#4078]: https://gitlab.freedesktop.org/drm/intel/issues/4078
[i915#4098]: https://gitlab.freedesktop.org/drm/intel/issues/4098
[i915#4103]: https://gitlab.freedesktop.org/drm/intel/issues/4103
[i915#4270]: https://gitlab.freedesktop.org/drm/intel/issues/4270
[i915#4281]: https://gitlab.freedesktop.org/drm/intel/issues/4281
[i915#4387]: https://gitlab.freedesktop.org/drm/intel/issues/4387
[i915#4613]: https://gitlab.freedesktop.org/drm/intel/issues/4613
[i915#4767]: https://gitlab.freedesktop.org/drm/intel/issues/4767
[i915#5176]: https://gitlab.freedesktop.org/drm/intel/issues/5176
[i915#5235]: https://gitlab.freedesktop.org/drm/intel/issues/5235
[i915#5286]: https://gitlab.freedesktop.org/drm/intel/issues/5286
[i915#5289]: https://gitlab.freedesktop.org/drm/intel/issues/5289
[i915#5325]: https://gitlab.freedesktop.org/drm/intel/issues/5325
[i915#5327]: https://gitlab.freedesktop.org/drm/intel/issues/5327
[i915#533]: https://gitlab.freedesktop.org/drm/intel/issues/533
[i915#5439]: https://gitlab.freedesktop.org/drm/intel/issues/5439
[i915#5784]: https://gitlab.freedesktop.org/drm/intel/issues/5784
[i915#6095]: https://gitlab.freedesktop.org/drm/intel/issues/6095
[i915#6117]: https://gitlab.freedesktop.org/drm/intel/issues/6117
[i915#6247]: https://gitlab.freedesktop.org/drm/intel/issues/6247
[i915#6248]: https://gitlab.freedesktop.org/drm/intel/issues/6248
[i915#6252]: https://gitlab.freedesktop.org/drm/intel/issues/6252
[i915#6268]: https://gitlab.freedesktop.org/drm/intel/issues/6268
[i915#6335]: https://gitlab.freedesktop.org/drm/intel/issues/6335
[i915#6355]: https://gitlab.freedesktop.org/drm/intel/issues/6355
[i915#6433]: https://gitlab.freedesktop.org/drm/intel/issues/6433
[i915#6497]: https://gitlab.freedesktop.org/drm/intel/issues/6497
[i915#658]: https://gitlab.freedesktop.org/drm/intel/issues/658
[i915#6768]: https://gitlab.freedesktop.org/drm/intel/issues/6768
[i915#6944]: https://gitlab.freedesktop.org/drm/intel/issues/6944
[i915#6946]: https://gitlab.freedesktop.org/drm/intel/issues/6946
[i915#6953]: https://gitlab.freedesktop.org/drm/intel/issues/6953
[i915#7052]: https://gitlab.freedesktop.org/drm/intel/issues/7052
[i915#7116]: https://gitlab.freedesktop.org/drm/intel/issues/7116
[i915#7118]: https://gitlab.freedesktop.org/drm/intel/issues/7118
[i915#7456]: https://gitlab.freedesktop.org/drm/intel/issues/7456
[i915#7561]: https://gitlab.freedesktop.org/drm/intel/issues/7561
[i915#7651]: https://gitlab.freedesktop.org/drm/intel/issues/7651
[i915#7679]: https://gitlab.freedesktop.org/drm/intel/issues/7679
[i915#7697]: https://gitlab.freedesktop.org/drm/intel/issues/7697
[i915#7742]: https://gitlab.freedesktop.org/drm/intel/issues/7742
Build changes
-------------
* Linux: CI_DRM_12554 -> Patchwork_112502v1
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_12554: 77b21315725079a0f62117b62ab9e6fc3c5b325d @ git://anongit.freedesktop.org/gfx-ci/linux
IGT_7110: db10a19b94d1d7ae5ba62eb48d52c47ccb27766f @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
Patchwork_112502v1: 77b21315725079a0f62117b62ab9e6fc3c5b325d @ git://anongit.freedesktop.org/gfx-ci/linux
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_112502v1/index.html
[-- Attachment #2: Type: text/html, Size: 16683 bytes --]
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
2023-01-07 15:15 [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag Arunpravin Paneer Selvam
2023-01-07 16:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-07 17:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
@ 2023-01-09 10:13 ` Christian König
2023-01-09 15:03 ` Alex Deucher
2023-01-10 12:02 ` Matthew Auld
3 siblings, 1 reply; 8+ messages in thread
From: Christian König @ 2023-01-09 10:13 UTC (permalink / raw)
To: Arunpravin Paneer Selvam, dri-devel, intel-gfx, amd-gfx,
matthew.auld, christian.koenig, alexander.deucher
Am 07.01.23 um 16:15 schrieb Arunpravin Paneer Selvam:
> As we are observing low numbers in viewperf graphics benchmark, we
> are strictly not allowing the top down flag enabled allocations
> to steal the memory space from cpu visible region.
>
> The approach is, we are sorting each order list entries in
> ascending order and compare the last entry of each order
> list in the freelist and return the max block.
>
> This patch improves the viewperf 3D benchmark scores.
>
> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Acked-by: Christian König <christian.koenig@amd.com>, but somebody with more insight of the drm buddy allocator should take a closer look at this.
> ---
> drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
> 1 file changed, 54 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
> index 11bb59399471..50916b2f2fc5 100644
> --- a/drivers/gpu/drm/drm_buddy.c
> +++ b/drivers/gpu/drm/drm_buddy.c
> @@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
> kmem_cache_free(slab_blocks, block);
> }
>
> +static void list_insert_sorted(struct drm_buddy *mm,
> + struct drm_buddy_block *block)
> +{
> + struct drm_buddy_block *node;
> + struct list_head *head;
> +
> + head = &mm->free_list[drm_buddy_block_order(block)];
> + if (list_empty(head)) {
> + list_add(&block->link, head);
> + return;
> + }
> +
> + list_for_each_entry(node, head, link)
> + if (drm_buddy_block_offset(block) < drm_buddy_block_offset(node))
> + break;
> +
> + __list_add(&block->link, node->link.prev, &node->link);
> +}
> +
> static void mark_allocated(struct drm_buddy_block *block)
> {
> block->header &= ~DRM_BUDDY_HEADER_STATE;
> @@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
> block->header &= ~DRM_BUDDY_HEADER_STATE;
> block->header |= DRM_BUDDY_FREE;
>
> - list_add(&block->link,
> - &mm->free_list[drm_buddy_block_order(block)]);
> + list_insert_sorted(mm, block);
> }
>
> static void mark_split(struct drm_buddy_block *block)
> @@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
> }
>
> static struct drm_buddy_block *
> -get_maxblock(struct list_head *head)
> +get_maxblock(struct drm_buddy *mm, unsigned int order)
> {
> struct drm_buddy_block *max_block = NULL, *node;
> + unsigned int i;
>
> - max_block = list_first_entry_or_null(head,
> - struct drm_buddy_block,
> - link);
> - if (!max_block)
> - return NULL;
> + for (i = order; i <= mm->max_order; ++i) {
> + if (!list_empty(&mm->free_list[i])) {
> + node = list_last_entry(&mm->free_list[i],
> + struct drm_buddy_block,
> + link);
> + if (!max_block) {
> + max_block = node;
> + continue;
> + }
>
> - list_for_each_entry(node, head, link) {
> - if (drm_buddy_block_offset(node) >
> - drm_buddy_block_offset(max_block))
> - max_block = node;
> + if (drm_buddy_block_offset(node) >
> + drm_buddy_block_offset(max_block)) {
> + max_block = node;
> + }
> + }
> }
>
> return max_block;
> @@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
> unsigned long flags)
> {
> struct drm_buddy_block *block = NULL;
> - unsigned int i;
> + unsigned int tmp;
> int err;
>
> - for (i = order; i <= mm->max_order; ++i) {
> - if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> - block = get_maxblock(&mm->free_list[i]);
> - if (block)
> - break;
> - } else {
> - block = list_first_entry_or_null(&mm->free_list[i],
> - struct drm_buddy_block,
> - link);
> - if (block)
> - break;
> + if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> + block = get_maxblock(mm, order);
> + if (block)
> + /* Store the obtained block order */
> + tmp = drm_buddy_block_order(block);
> + } else {
> + for (tmp = order; tmp <= mm->max_order; ++tmp) {
> + if (!list_empty(&mm->free_list[tmp])) {
> + block = list_last_entry(&mm->free_list[tmp],
> + struct drm_buddy_block,
> + link);
> + if (block)
> + break;
> + }
> }
> }
>
> @@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
>
> BUG_ON(!drm_buddy_block_is_free(block));
>
> - while (i != order) {
> + while (tmp != order) {
> err = split_block(mm, block);
> if (unlikely(err))
> goto err_undo;
>
> block = block->right;
> - i--;
> + tmp--;
> }
> return block;
>
> err_undo:
> - if (i != order)
> + if (tmp != order)
> __drm_buddy_free(mm, block);
> return ERR_PTR(err);
> }
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
2023-01-09 10:13 ` [Intel-gfx] [PATCH] " Christian König
@ 2023-01-09 15:03 ` Alex Deucher
0 siblings, 0 replies; 8+ messages in thread
From: Alex Deucher @ 2023-01-09 15:03 UTC (permalink / raw)
To: Christian König
Cc: dri-devel, Arunpravin Paneer Selvam, intel-gfx, amd-gfx,
matthew.auld, alexander.deucher, christian.koenig
On Mon, Jan 9, 2023 at 5:13 AM Christian König
<ckoenig.leichtzumerken@gmail.com> wrote:
>
> Am 07.01.23 um 16:15 schrieb Arunpravin Paneer Selvam:
> > As we are observing low numbers in viewperf graphics benchmark, we
> > are strictly not allowing the top down flag enabled allocations
> > to steal the memory space from cpu visible region.
> >
> > The approach is, we are sorting each order list entries in
> > ascending order and compare the last entry of each order
> > list in the freelist and return the max block.
> >
> > This patch improves the viewperf 3D benchmark scores.
> >
> > Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
>
> Acked-by: Christian König <christian.koenig@amd.com>, but somebody with more insight of the drm buddy allocator should take a closer look at this.
I'm not a drm_buddy expert either, but this patch fixes a lot of
issues on both dGPUs and APUs:
Acked-by: Alex Deucher <alexander.deucher@amd.com>
>
>
> > ---
> > drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
> > 1 file changed, 54 insertions(+), 27 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
> > index 11bb59399471..50916b2f2fc5 100644
> > --- a/drivers/gpu/drm/drm_buddy.c
> > +++ b/drivers/gpu/drm/drm_buddy.c
> > @@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
> > kmem_cache_free(slab_blocks, block);
> > }
> >
> > +static void list_insert_sorted(struct drm_buddy *mm,
> > + struct drm_buddy_block *block)
> > +{
> > + struct drm_buddy_block *node;
> > + struct list_head *head;
> > +
> > + head = &mm->free_list[drm_buddy_block_order(block)];
> > + if (list_empty(head)) {
> > + list_add(&block->link, head);
> > + return;
> > + }
> > +
> > + list_for_each_entry(node, head, link)
> > + if (drm_buddy_block_offset(block) < drm_buddy_block_offset(node))
> > + break;
> > +
> > + __list_add(&block->link, node->link.prev, &node->link);
> > +}
> > +
> > static void mark_allocated(struct drm_buddy_block *block)
> > {
> > block->header &= ~DRM_BUDDY_HEADER_STATE;
> > @@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
> > block->header &= ~DRM_BUDDY_HEADER_STATE;
> > block->header |= DRM_BUDDY_FREE;
> >
> > - list_add(&block->link,
> > - &mm->free_list[drm_buddy_block_order(block)]);
> > + list_insert_sorted(mm, block);
> > }
> >
> > static void mark_split(struct drm_buddy_block *block)
> > @@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
> > }
> >
> > static struct drm_buddy_block *
> > -get_maxblock(struct list_head *head)
> > +get_maxblock(struct drm_buddy *mm, unsigned int order)
> > {
> > struct drm_buddy_block *max_block = NULL, *node;
> > + unsigned int i;
> >
> > - max_block = list_first_entry_or_null(head,
> > - struct drm_buddy_block,
> > - link);
> > - if (!max_block)
> > - return NULL;
> > + for (i = order; i <= mm->max_order; ++i) {
> > + if (!list_empty(&mm->free_list[i])) {
> > + node = list_last_entry(&mm->free_list[i],
> > + struct drm_buddy_block,
> > + link);
> > + if (!max_block) {
> > + max_block = node;
> > + continue;
> > + }
> >
> > - list_for_each_entry(node, head, link) {
> > - if (drm_buddy_block_offset(node) >
> > - drm_buddy_block_offset(max_block))
> > - max_block = node;
> > + if (drm_buddy_block_offset(node) >
> > + drm_buddy_block_offset(max_block)) {
> > + max_block = node;
> > + }
> > + }
> > }
> >
> > return max_block;
> > @@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
> > unsigned long flags)
> > {
> > struct drm_buddy_block *block = NULL;
> > - unsigned int i;
> > + unsigned int tmp;
> > int err;
> >
> > - for (i = order; i <= mm->max_order; ++i) {
> > - if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> > - block = get_maxblock(&mm->free_list[i]);
> > - if (block)
> > - break;
> > - } else {
> > - block = list_first_entry_or_null(&mm->free_list[i],
> > - struct drm_buddy_block,
> > - link);
> > - if (block)
> > - break;
> > + if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> > + block = get_maxblock(mm, order);
> > + if (block)
> > + /* Store the obtained block order */
> > + tmp = drm_buddy_block_order(block);
> > + } else {
> > + for (tmp = order; tmp <= mm->max_order; ++tmp) {
> > + if (!list_empty(&mm->free_list[tmp])) {
> > + block = list_last_entry(&mm->free_list[tmp],
> > + struct drm_buddy_block,
> > + link);
> > + if (block)
> > + break;
> > + }
> > }
> > }
> >
> > @@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
> >
> > BUG_ON(!drm_buddy_block_is_free(block));
> >
> > - while (i != order) {
> > + while (tmp != order) {
> > err = split_block(mm, block);
> > if (unlikely(err))
> > goto err_undo;
> >
> > block = block->right;
> > - i--;
> > + tmp--;
> > }
> > return block;
> >
> > err_undo:
> > - if (i != order)
> > + if (tmp != order)
> > __drm_buddy_free(mm, block);
> > return ERR_PTR(err);
> > }
>
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
2023-01-07 15:15 [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag Arunpravin Paneer Selvam
` (2 preceding siblings ...)
2023-01-09 10:13 ` [Intel-gfx] [PATCH] " Christian König
@ 2023-01-10 12:02 ` Matthew Auld
2023-01-10 15:26 ` Arunpravin Paneer Selvam
2023-01-10 15:50 ` Matthew Auld
3 siblings, 2 replies; 8+ messages in thread
From: Matthew Auld @ 2023-01-10 12:02 UTC (permalink / raw)
To: Arunpravin Paneer Selvam, dri-devel, intel-gfx, amd-gfx,
christian.koenig, alexander.deucher
On 07/01/2023 15:15, Arunpravin Paneer Selvam wrote:
> As we are observing low numbers in viewperf graphics benchmark, we
> are strictly not allowing the top down flag enabled allocations
> to steal the memory space from cpu visible region.
>
> The approach is, we are sorting each order list entries in
> ascending order and compare the last entry of each order
> list in the freelist and return the max block.
Did you also run the selftests? Does everything still pass and complete
in a reasonable amount of time?
>
> This patch improves the viewperf 3D benchmark scores.
>
> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
> ---
> drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
> 1 file changed, 54 insertions(+), 27 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
> index 11bb59399471..50916b2f2fc5 100644
> --- a/drivers/gpu/drm/drm_buddy.c
> +++ b/drivers/gpu/drm/drm_buddy.c
> @@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
> kmem_cache_free(slab_blocks, block);
> }
>
> +static void list_insert_sorted(struct drm_buddy *mm,
> + struct drm_buddy_block *block)
> +{
> + struct drm_buddy_block *node;
> + struct list_head *head;
> +
> + head = &mm->free_list[drm_buddy_block_order(block)];
> + if (list_empty(head)) {
> + list_add(&block->link, head);
> + return;
> + }
> +
> + list_for_each_entry(node, head, link)
> + if (drm_buddy_block_offset(block) < drm_buddy_block_offset(node))
> + break;
> +
> + __list_add(&block->link, node->link.prev, &node->link);
> +}
> +
> static void mark_allocated(struct drm_buddy_block *block)
> {
> block->header &= ~DRM_BUDDY_HEADER_STATE;
> @@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
> block->header &= ~DRM_BUDDY_HEADER_STATE;
> block->header |= DRM_BUDDY_FREE;
>
> - list_add(&block->link,
> - &mm->free_list[drm_buddy_block_order(block)]);
> + list_insert_sorted(mm, block);
One advantage of not sorting is when splitting down a large block.
Previously the most-recently-split would be at the start of the list for
the next order down, where potentially the next allocation could use it.
So perhaps less fragmentation if it's all part of one BO. Otherwise I
don't see any other downsides, other than the extra overhead of sorting.
> }
>
> static void mark_split(struct drm_buddy_block *block)
> @@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
> }
>
> static struct drm_buddy_block *
> -get_maxblock(struct list_head *head)
> +get_maxblock(struct drm_buddy *mm, unsigned int order)
> {
> struct drm_buddy_block *max_block = NULL, *node;
> + unsigned int i;
>
> - max_block = list_first_entry_or_null(head,
> - struct drm_buddy_block,
> - link);
> - if (!max_block)
> - return NULL;
> + for (i = order; i <= mm->max_order; ++i) {
> + if (!list_empty(&mm->free_list[i])) {
> + node = list_last_entry(&mm->free_list[i],
> + struct drm_buddy_block,
> + link);
> + if (!max_block) {
> + max_block = node;
> + continue;
> + }
>
> - list_for_each_entry(node, head, link) {
> - if (drm_buddy_block_offset(node) >
> - drm_buddy_block_offset(max_block))
> - max_block = node;
> + if (drm_buddy_block_offset(node) >
> + drm_buddy_block_offset(max_block)) {
Formatting doesn't look right here.
Going to test this today with some workloads with small-bar and i915
just to see if this improves/impacts anything for us.
> + max_block = node;
> + }
> + }
> }
>
> return max_block;
> @@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
> unsigned long flags)
> {
> struct drm_buddy_block *block = NULL;
> - unsigned int i;
> + unsigned int tmp;
> int err;
>
> - for (i = order; i <= mm->max_order; ++i) {
> - if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> - block = get_maxblock(&mm->free_list[i]);
> - if (block)
> - break;
> - } else {
> - block = list_first_entry_or_null(&mm->free_list[i],
> - struct drm_buddy_block,
> - link);
> - if (block)
> - break;
> + if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
> + block = get_maxblock(mm, order);
> + if (block)
> + /* Store the obtained block order */
> + tmp = drm_buddy_block_order(block);
> + } else {
> + for (tmp = order; tmp <= mm->max_order; ++tmp) {
> + if (!list_empty(&mm->free_list[tmp])) {
> + block = list_last_entry(&mm->free_list[tmp],
> + struct drm_buddy_block,
> + link);
> + if (block)
> + break;
> + }
> }
> }
>
> @@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
>
> BUG_ON(!drm_buddy_block_is_free(block));
>
> - while (i != order) {
> + while (tmp != order) {
> err = split_block(mm, block);
> if (unlikely(err))
> goto err_undo;
>
> block = block->right;
> - i--;
> + tmp--;
> }
> return block;
>
> err_undo:
> - if (i != order)
> + if (tmp != order)
> __drm_buddy_free(mm, block);
> return ERR_PTR(err);
> }
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
2023-01-10 12:02 ` Matthew Auld
@ 2023-01-10 15:26 ` Arunpravin Paneer Selvam
2023-01-10 15:50 ` Matthew Auld
1 sibling, 0 replies; 8+ messages in thread
From: Arunpravin Paneer Selvam @ 2023-01-10 15:26 UTC (permalink / raw)
To: Matthew Auld, dri-devel, intel-gfx, amd-gfx, christian.koenig,
alexander.deucher
Hi Matthew,
On 1/10/2023 5:32 PM, Matthew Auld wrote:
> On 07/01/2023 15:15, Arunpravin Paneer Selvam wrote:
>> As we are observing low numbers in viewperf graphics benchmark, we
>> are strictly not allowing the top down flag enabled allocations
>> to steal the memory space from cpu visible region.
>>
>> The approach is, we are sorting each order list entries in
>> ascending order and compare the last entry of each order
>> list in the freelist and return the max block.
>
> Did you also run the selftests? Does everything still pass and
> complete in a reasonable amount of time?
> I will try giving a run
>>
>> This patch improves the viewperf 3D benchmark scores.
>>
>> Signed-off-by: Arunpravin Paneer Selvam
>> <Arunpravin.PaneerSelvam@amd.com>
>> ---
>> drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
>> 1 file changed, 54 insertions(+), 27 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
>> index 11bb59399471..50916b2f2fc5 100644
>> --- a/drivers/gpu/drm/drm_buddy.c
>> +++ b/drivers/gpu/drm/drm_buddy.c
>> @@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
>> kmem_cache_free(slab_blocks, block);
>> }
>> +static void list_insert_sorted(struct drm_buddy *mm,
>> + struct drm_buddy_block *block)
>> +{
>> + struct drm_buddy_block *node;
>> + struct list_head *head;
>> +
>> + head = &mm->free_list[drm_buddy_block_order(block)];
>> + if (list_empty(head)) {
>> + list_add(&block->link, head);
>> + return;
>> + }
>> +
>> + list_for_each_entry(node, head, link)
>> + if (drm_buddy_block_offset(block) <
>> drm_buddy_block_offset(node))
>> + break;
>> +
>> + __list_add(&block->link, node->link.prev, &node->link);
>> +}
>> +
>> static void mark_allocated(struct drm_buddy_block *block)
>> {
>> block->header &= ~DRM_BUDDY_HEADER_STATE;
>> @@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
>> block->header &= ~DRM_BUDDY_HEADER_STATE;
>> block->header |= DRM_BUDDY_FREE;
>> - list_add(&block->link,
>> - &mm->free_list[drm_buddy_block_order(block)]);
>> + list_insert_sorted(mm, block);
>
> One advantage of not sorting is when splitting down a large block.
> Previously the most-recently-split would be at the start of the list
> for the next order down, where potentially the next allocation could
> use it. So perhaps less fragmentation if it's all part of one BO.
> Otherwise I don't see any other downsides, other than the extra
> overhead of sorting.
>
Allocating from freelist is traversing through right side (i.e top most
address range) and for TOPDOWN flag allocations we just split the top
most large block once and the subsequent TOPDOWN low order allocations
would get block from same already split large block
For the normal allocations, I modified to retrieve the blocks in each
order list from the last entry which has the high probability of getting
top most blocks as we have sorted the blocks in each order list.
Thus the bottom most large blocks are not frequently used, hence we have
more space for the visible region on dGPU.
For APU which has small sized VRAM space, the allocations are now
ordered and we don't allocate randomly from freelist solving
fragmentation issues.
>> }
>> static void mark_split(struct drm_buddy_block *block)
>> @@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
>> }
>> static struct drm_buddy_block *
>> -get_maxblock(struct list_head *head)
>> +get_maxblock(struct drm_buddy *mm, unsigned int order)
>> {
>> struct drm_buddy_block *max_block = NULL, *node;
>> + unsigned int i;
>> - max_block = list_first_entry_or_null(head,
>> - struct drm_buddy_block,
>> - link);
>> - if (!max_block)
>> - return NULL;
>> + for (i = order; i <= mm->max_order; ++i) {
>> + if (!list_empty(&mm->free_list[i])) {
>> + node = list_last_entry(&mm->free_list[i],
>> + struct drm_buddy_block,
>> + link);
>> + if (!max_block) {
>> + max_block = node;
>> + continue;
>> + }
>> - list_for_each_entry(node, head, link) {
>> - if (drm_buddy_block_offset(node) >
>> - drm_buddy_block_offset(max_block))
>> - max_block = node;
>> + if (drm_buddy_block_offset(node) >
>> + drm_buddy_block_offset(max_block)) {
>
> Formatting doesn't look right here.
I will check.
>
> Going to test this today with some workloads with small-bar and i915
> just to see if this improves/impacts anything for us.
>
>> + max_block = node;
>> + }
>> + }
>> }
>> return max_block;
>> @@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
>> unsigned long flags)
>> {
>> struct drm_buddy_block *block = NULL;
>> - unsigned int i;
>> + unsigned int tmp;
>> int err;
>> - for (i = order; i <= mm->max_order; ++i) {
>> - if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
>> - block = get_maxblock(&mm->free_list[i]);
>> - if (block)
>> - break;
>> - } else {
>> - block = list_first_entry_or_null(&mm->free_list[i],
>> - struct drm_buddy_block,
>> - link);
>> - if (block)
>> - break;
>> + if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
>> + block = get_maxblock(mm, order);
>> + if (block)
>> + /* Store the obtained block order */
>> + tmp = drm_buddy_block_order(block);
>> + } else {
>> + for (tmp = order; tmp <= mm->max_order; ++tmp) {
>> + if (!list_empty(&mm->free_list[tmp])) {
>> + block = list_last_entry(&mm->free_list[tmp],
>> + struct drm_buddy_block,
>> + link);
>> + if (block)
>> + break;
>> + }
>> }
>> }
>> @@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
>> BUG_ON(!drm_buddy_block_is_free(block));
>> - while (i != order) {
>> + while (tmp != order) {
>> err = split_block(mm, block);
>> if (unlikely(err))
>> goto err_undo;
>> block = block->right;
>> - i--;
>> + tmp--;
>> }
>> return block;
>> err_undo:
>> - if (i != order)
>> + if (tmp != order)
>> __drm_buddy_free(mm, block);
>> return ERR_PTR(err);
>> }
^ permalink raw reply [flat|nested] 8+ messages in thread
* Re: [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag
2023-01-10 12:02 ` Matthew Auld
2023-01-10 15:26 ` Arunpravin Paneer Selvam
@ 2023-01-10 15:50 ` Matthew Auld
1 sibling, 0 replies; 8+ messages in thread
From: Matthew Auld @ 2023-01-10 15:50 UTC (permalink / raw)
To: Arunpravin Paneer Selvam, dri-devel, intel-gfx, amd-gfx,
christian.koenig, alexander.deucher
On 10/01/2023 12:02, Matthew Auld wrote:
> On 07/01/2023 15:15, Arunpravin Paneer Selvam wrote:
>> As we are observing low numbers in viewperf graphics benchmark, we
>> are strictly not allowing the top down flag enabled allocations
>> to steal the memory space from cpu visible region.
>>
>> The approach is, we are sorting each order list entries in
>> ascending order and compare the last entry of each order
>> list in the freelist and return the max block.
>
> Did you also run the selftests? Does everything still pass and complete
> in a reasonable amount of time?
>
>>
>> This patch improves the viewperf 3D benchmark scores.
>>
>> Signed-off-by: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
>> ---
>> drivers/gpu/drm/drm_buddy.c | 81 ++++++++++++++++++++++++-------------
>> 1 file changed, 54 insertions(+), 27 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_buddy.c b/drivers/gpu/drm/drm_buddy.c
>> index 11bb59399471..50916b2f2fc5 100644
>> --- a/drivers/gpu/drm/drm_buddy.c
>> +++ b/drivers/gpu/drm/drm_buddy.c
>> @@ -38,6 +38,25 @@ static void drm_block_free(struct drm_buddy *mm,
>> kmem_cache_free(slab_blocks, block);
>> }
>> +static void list_insert_sorted(struct drm_buddy *mm,
>> + struct drm_buddy_block *block)
>> +{
>> + struct drm_buddy_block *node;
>> + struct list_head *head;
>> +
>> + head = &mm->free_list[drm_buddy_block_order(block)];
>> + if (list_empty(head)) {
>> + list_add(&block->link, head);
>> + return;
>> + }
>> +
>> + list_for_each_entry(node, head, link)
>> + if (drm_buddy_block_offset(block) <
>> drm_buddy_block_offset(node))
>> + break;
>> +
>> + __list_add(&block->link, node->link.prev, &node->link);
>> +}
>> +
>> static void mark_allocated(struct drm_buddy_block *block)
>> {
>> block->header &= ~DRM_BUDDY_HEADER_STATE;
>> @@ -52,8 +71,7 @@ static void mark_free(struct drm_buddy *mm,
>> block->header &= ~DRM_BUDDY_HEADER_STATE;
>> block->header |= DRM_BUDDY_FREE;
>> - list_add(&block->link,
>> - &mm->free_list[drm_buddy_block_order(block)]);
>> + list_insert_sorted(mm, block);
>
> One advantage of not sorting is when splitting down a large block.
> Previously the most-recently-split would be at the start of the list for
> the next order down, where potentially the next allocation could use it.
> So perhaps less fragmentation if it's all part of one BO. Otherwise I
> don't see any other downsides, other than the extra overhead of sorting.
>
>> }
>> static void mark_split(struct drm_buddy_block *block)
>> @@ -387,20 +405,26 @@ alloc_range_bias(struct drm_buddy *mm,
>> }
>> static struct drm_buddy_block *
>> -get_maxblock(struct list_head *head)
>> +get_maxblock(struct drm_buddy *mm, unsigned int order)
>> {
>> struct drm_buddy_block *max_block = NULL, *node;
>> + unsigned int i;
>> - max_block = list_first_entry_or_null(head,
>> - struct drm_buddy_block,
>> - link);
>> - if (!max_block)
>> - return NULL;
>> + for (i = order; i <= mm->max_order; ++i) {
>> + if (!list_empty(&mm->free_list[i])) {
>> + node = list_last_entry(&mm->free_list[i],
>> + struct drm_buddy_block,
>> + link);
>> + if (!max_block) {
>> + max_block = node;
>> + continue;
>> + }
>> - list_for_each_entry(node, head, link) {
>> - if (drm_buddy_block_offset(node) >
>> - drm_buddy_block_offset(max_block))
>> - max_block = node;
>> + if (drm_buddy_block_offset(node) >
>> + drm_buddy_block_offset(max_block)) {
>
> Formatting doesn't look right here.
>
> Going to test this today with some workloads with small-bar and i915
> just to see if this improves/impacts anything for us.
No surprises, and as advertised seems to lead to reduced utilisation of
the mappable part for buffers that don't explicitly need it (TOPDOWN).
Assuming the selftests are still happy,
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
>
>> + max_block = node;
>> + }
>> + }
>> }
>> return max_block;
>> @@ -412,20 +436,23 @@ alloc_from_freelist(struct drm_buddy *mm,
>> unsigned long flags)
>> {
>> struct drm_buddy_block *block = NULL;
>> - unsigned int i;
>> + unsigned int tmp;
>> int err;
>> - for (i = order; i <= mm->max_order; ++i) {
>> - if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
>> - block = get_maxblock(&mm->free_list[i]);
>> - if (block)
>> - break;
>> - } else {
>> - block = list_first_entry_or_null(&mm->free_list[i],
>> - struct drm_buddy_block,
>> - link);
>> - if (block)
>> - break;
>> + if (flags & DRM_BUDDY_TOPDOWN_ALLOCATION) {
>> + block = get_maxblock(mm, order);
>> + if (block)
>> + /* Store the obtained block order */
>> + tmp = drm_buddy_block_order(block);
>> + } else {
>> + for (tmp = order; tmp <= mm->max_order; ++tmp) {
>> + if (!list_empty(&mm->free_list[tmp])) {
>> + block = list_last_entry(&mm->free_list[tmp],
>> + struct drm_buddy_block,
>> + link);
>> + if (block)
>> + break;
>> + }
>> }
>> }
>> @@ -434,18 +461,18 @@ alloc_from_freelist(struct drm_buddy *mm,
>> BUG_ON(!drm_buddy_block_is_free(block));
>> - while (i != order) {
>> + while (tmp != order) {
>> err = split_block(mm, block);
>> if (unlikely(err))
>> goto err_undo;
>> block = block->right;
>> - i--;
>> + tmp--;
>> }
>> return block;
>> err_undo:
>> - if (i != order)
>> + if (tmp != order)
>> __drm_buddy_free(mm, block);
>> return ERR_PTR(err);
>> }
^ permalink raw reply [flat|nested] 8+ messages in thread
end of thread, other threads:[~2023-01-10 15:50 UTC | newest]
Thread overview: 8+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-01-07 15:15 [Intel-gfx] [PATCH] drm: Alloc high address for drm buddy topdown flag Arunpravin Paneer Selvam
2023-01-07 16:08 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2023-01-07 17:30 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2023-01-09 10:13 ` [Intel-gfx] [PATCH] " Christian König
2023-01-09 15:03 ` Alex Deucher
2023-01-10 12:02 ` Matthew Auld
2023-01-10 15:26 ` Arunpravin Paneer Selvam
2023-01-10 15:50 ` Matthew Auld
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox