diff options
| author | Tejun Heo <tj@kernel.org> | 2025-09-23 22:03:26 +0300 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-11-02 16:18:04 +0300 |
| commit | a0ba52a5a1bb3975b62b5a70ac39cce6476dfaa9 (patch) | |
| tree | 122f1cb6f7b77d43b1f08cf3cb894b710cd47511 /scripts/gdb/linux/xarray.py | |
| parent | feec2bf6e1e93586699837f57a30e395ff18f763 (diff) | |
| download | linux-a0ba52a5a1bb3975b62b5a70ac39cce6476dfaa9.tar.xz | |
sched_ext: Make qmap dump operation non-destructive
[ Upstream commit d452972858e5cfa4262320ab74fe8f016460b96f ]
The qmap dump operation was destructively consuming queue entries while
displaying them. As dump can be triggered anytime, this can easily lead to
stalls. Add a temporary dump_store queue and modify the dump logic to pop
entries, display them, and then restore them back to the original queue.
This allows dump operations to be performed without affecting the
scheduler's queue state.
Note that if racing against new enqueues during dump, ordering can get
mixed up, but this is acceptable for debugging purposes.
Acked-by: Andrea Righi <arighi@nvidia.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'scripts/gdb/linux/xarray.py')
0 files changed, 0 insertions, 0 deletions