From: "Christian König" <christian.koenig@amd.com>
To: Harry Wentland <harry.wentland@amd.com>,
"Kazlauskas, Nicholas" <Nicholas.Kazlauskas@amd.com>,
"Yu, Lang" <Lang.Yu@amd.com>
Cc: "Michel Dänzer" <michel@daenzer.net>,
"amd-gfx list" <amd-gfx@lists.freedesktop.org>,
"Daniel Vetter" <daniel@ffwll.ch>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: Questions about KMS flip
Date: Fri, 12 Nov 2021 13:47:43 +0100 [thread overview]
Message-ID: <ab2fb071-12ab-da99-53c9-1411ca9acdaa@amd.com> (raw)
In-Reply-To: <YYvIfXy9bwPokiK9@phenom.ffwll.local>
Hi guys,
Am 10.11.21 um 14:26 schrieb Daniel Vetter:
> [SNIP]
> stack depot, not stuff it into a string. stack depot is a lot more
> efficient and capturing backtraces, since it de-dupes and hashes and all
> you need is a pointer iirc. linux/stackdepot.h for interface, I think we
> recently gained a few more users of it in drm. It's _really_ nifty.
> -Daniel
thanks for the pointer Daniel, that framework indeed looks like it can
become handy.
Anyway this unfortunately turned out to be work for Harray and Nicholas.
In detail it's about this bug report here:
https://bugzilla.kernel.org/show_bug.cgi?id=214621
Lang was able to reproduce the issue and narrow it down to the pin in
amdgpu_display_crtc_page_flip_target().
In other words we somehow have an unbalanced pinning of the scanout
buffer in DC.
What should we do about that?
Regards,
Christian.
next parent reply other threads:[~2021-11-12 12:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <579d0f44-bb85-11b2-d326-35a0b7c5d0de@amd.com>
[not found] ` <5c242319-ade3-5621-6429-f77b17c34de5@amd.com>
[not found] ` <YYV0W1CxT5torU7u@phenom.ffwll.local>
[not found] ` <64e70779-7c33-7849-aa29-aeaee4a89005@amd.com>
[not found] ` <YYk7SkflDx8ToqYG@phenom.ffwll.local>
[not found] ` <4ba7e3f8-7956-882a-6888-57e2448b907d@amd.com>
[not found] ` <YYvIfXy9bwPokiK9@phenom.ffwll.local>
2021-11-12 12:47 ` Christian König [this message]
2021-11-12 14:29 ` Questions about KMS flip Michel Dänzer
2021-11-12 14:30 ` Michel Dänzer
2021-11-12 15:03 ` Christian König
2021-11-12 16:10 ` Michel Dänzer
2021-11-15 6:41 ` Lang Yu
2021-11-15 8:38 ` Michel Dänzer
2021-11-15 9:04 ` Lang Yu
2021-11-15 9:49 ` Michel Dänzer
2021-11-15 11:31 ` Lang Yu
2021-11-15 12:04 ` Michel Dänzer
2021-11-16 3:27 ` Lang Yu
2021-11-16 7:14 ` Christian König
2021-11-16 8:00 ` Lang Yu
2021-11-16 8:09 ` Christian König
2021-11-16 14:10 ` Alex Deucher
2021-11-16 14:50 ` Michel Dänzer
2021-11-15 7:25 ` 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=ab2fb071-12ab-da99-53c9-1411ca9acdaa@amd.com \
--to=christian.koenig@amd.com \
--cc=Lang.Yu@amd.com \
--cc=Nicholas.Kazlauskas@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
--cc=michel@daenzer.net \
/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