From: Dieter Faulbaum <dieter@faulbaum.in-berlin.de>
To: Philip Yang <yangp@amd.com>
Cc: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
"Philip Yang" <Philip.Yang@amd.com>,
amd-gfx@lists.freedesktop.org, Felix.Kuehling@amd.com,
Alexander.Deucher@amd.com, christian.koenig@amd.com,
regressions@lists.linux.dev
Subject: Re: [PATCH v2 4/9] drm/amdkfd: Validate user queue buffers
Date: Fri, 14 Mar 2025 12:06:18 +0100 [thread overview]
Message-ID: <rie1puzeus5.fsf@faulbaum.in-berlin.de> (raw)
In-Reply-To: <315e27ab-f1d1-a681-a32f-1fc28cd81193@amd.com> (Philip Yang's message of "Wed, 12 Feb 2025 18:02:15 -0500")
Hello Philip,
Philip Yang <yangp@amd.com> writes:
> On 2025-02-12 17:42, Uwe Kleine-König wrote:
>
> #regzbot introduced: 68e599db7a549f010a329515f3508d8a8c3467a4
> #regzbot monitor: https://bugs.debian.org/1093124
>
> Hello,
>
> On Thu, Jul 18, 2024 at 05:05:53PM -0400, Philip Yang wrote:
>
> 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.Yang@amd.com>
> Reviewed-by: Felix Kuehling <felix.kuehling@amd.com>
>
>
> This change made it into v6.12-rc1 as 68e599db7a54 ("drm/amdkfd:
> Validate user queue buffers"). A Debian user (Dieter Faulbaum,
> on Cc)
> reported that this change introduced a regression using a gfx803
> device
> resulting in a HSA exception when e.g. darktable is used. I
> didn't even
> try to understand the problem, but maybe one of you have an idea
> about
> the issue?!
>
> Try this patch
>
> https://lore.kernel.org/all/20250130000412.29812-1-Philip.Yang@amd.com/T/
It seems for me, that your patch isn't applied in the mainline
kernel.
What do you think, will it once happen?-)
Is it falling through cracks?
With regards
Dieter
next prev parent reply other threads:[~2025-03-14 12:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 21:05 [PATCH v2 0/9] KFD user queue validation Philip Yang
2024-07-18 21:05 ` [PATCH v2 1/9] drm/amdkfd: kfd_bo_mapped_dev support partition Philip Yang
2024-07-18 21:05 ` [PATCH v2 2/9] drm/amdkfd: amdkfd_free_gtt_mem clear the correct pointer Philip Yang
2024-07-18 21:05 ` [PATCH v2 3/9] drm/amdkfd: Refactor queue wptr_bo GART mapping Philip Yang
2024-07-18 21:05 ` [PATCH v2 4/9] drm/amdkfd: Validate user queue buffers Philip Yang
2025-02-12 22:42 ` Uwe Kleine-König
2025-02-12 23:02 ` Philip Yang
2025-02-13 8:43 ` Uwe Kleine-König
2025-02-13 9:56 ` Dieter Faulbaum
2025-03-14 11:06 ` Dieter Faulbaum [this message]
2025-03-14 13:12 ` Alex Deucher
2024-07-18 21:05 ` [PATCH v2 5/9] drm/amdkfd: Ensure user queue buffers residency Philip Yang
2024-07-18 21:05 ` [PATCH v2 6/9] drm/amdkfd: Validate user queue svm memory residency Philip Yang
2024-07-18 21:05 ` [PATCH v2 7/9] drm/amdkfd: Validate user queue update Philip Yang
2024-07-18 21:05 ` [PATCH v2 8/9] drm/amdkfd: Store queue cwsr area size to node properties Philip Yang
2024-07-18 21:05 ` [PATCH v2 9/9] drm/amdkfd: Validate queue cwsr area and eop buffer size Philip Yang
2024-07-18 21:12 ` [PATCH v2 0/9] KFD user queue validation Felix Kuehling
2024-07-19 8:45 ` Christian König
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=rie1puzeus5.fsf@faulbaum.in-berlin.de \
--to=dieter@faulbaum.in-berlin.de \
--cc=Alexander.Deucher@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=regressions@lists.linux.dev \
--cc=u.kleine-koenig@baylibre.com \
--cc=yangp@amd.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.