Hello Uwe,
Thank you for your patience and help!
Uwe Kleine-König <uklei...@debian.org> writes:
git bisect skip
gets you out of that. It makes git select a different revision
to test for you. If needed repeat it.
`git bisect skip` the thing to do in general if you cannot find
out for a suggested revision if the problem is in there or not.
Something like that shouldn't happen, but it does at times. That
makes the bisection a bit ineffective, but typically it
converges anyhow. Alternatively you can try to be smart about
the selection of the next revision to test and just do git
checkout of an alternative revision.
(after some skips) this should be the "bad" one:
68e599db7a549f010a329515f3508d8a8c3467a4 is the first bad commit
commit 68e599db7a549f010a329515f3508d8a8c3467a4 (HEAD)
Author: Philip Yang <philip.y...@amd.com>
Date: Thu Jun 20 12:21:57 2024 -0400
drm/amdkfd: Validate user queue buffers
Find user queue rptr, ring buf, eop buffer and cwsr area BOs,
and
check BOs are mapped on the GPU with correct size and take the
BO
reference.
Signed-off-by: Philip Yang <philip.y...@amd.com>
Reviewed-by: Felix Kuehling <felix.kuehl...@amd.com>
Acked-by: Christian König <christian.koe...@amd.com>
Signed-off-by: Alex Deucher <alexander.deuc...@amd.com>
drivers/gpu/drm/amd/amdkfd/kfd_priv.h | 4 ++++
drivers/gpu/drm/amd/amdkfd/kfd_queue.c | 38
++++++++++++++++++++++++++++++++++++--
2 files changed, 40 insertions(+), 2 deletions(-)
With regards
Dieter
