From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Lu Yao <yaolu@kylinos.cn>,
alexander.deucher@amd.com, christian.koenig@amd.com,
Xinhui.Pan@amd.com, srinivasan.shanmugam@amd.com,
sunil.khatri@amd.com
Cc: airlied@gmail.com, daniel@ffwll.ch,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: add dce6 drm_panic support
Date: Fri, 2 Aug 2024 11:39:36 +0200 [thread overview]
Message-ID: <ce45d800-ad6a-4cef-9c57-480908867490@gmail.com> (raw)
In-Reply-To: <20240802071752.116541-1-yaolu@kylinos.cn>
Am 02.08.24 um 09:17 schrieb Lu Yao:
> Add support for the drm_panic module, which displays a pretty user
> friendly message on the screen when a Linux kernel panic occurs.
>
> Signed-off-by: Lu Yao <yaolu@kylinos.cn>
> ---
> The patch can work properly on the TTY, but after start X, drawn
> image is messy, it looks like the data isn't linearly arranged.
> However at this time 'fb->modifier' is 'DRM_FORMAT_MOD_LINEAR'.
>
> Another difference I found is:
> For TTY, the amdgpu_bo is created with flag
> 'AMDGPU_GEM_CREATE_CPU_ACCESS_REQUIRED|AMDGPU_GEM_CREATE_CPU_GTT_USWC|
> AMDGPU_GEM_CREATE_VRAM_CLEARED|AMDGPU_GEM_CREATE_VRAM_CONTIGUOUS'.
> For X, the amdgpu_bo is created with flag
> 'AMDGPU_GEM_CREATE_NO_CPU_ACCESS|AMDGPU_GEM_CREATE_CPU_GTT_USWC'
> I try to use same flag for X, it looks like no difference.
>
> Can someone provide some insight into this problem or where I am going
> wrong. Thanks a lot.
>
> Test environment: X86 arch + v6.6 kernel + R7340.
> ---
> drivers/gpu/drm/amd/amdgpu/dce_v6_0.c | 32 +++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c b/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
> index 05c0df97f01d..12c3801c264a 100644
> --- a/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
> +++ b/drivers/gpu/drm/amd/amdgpu/dce_v6_0.c
> @@ -28,6 +28,8 @@
> #include <drm/drm_modeset_helper.h>
> #include <drm/drm_modeset_helper_vtables.h>
> #include <drm/drm_vblank.h>
> +#include <drm/drm_panic.h>
> +#include "../../drm_internal.h"
Well that this file is named "internal" and not in a common include
directory is a strong indicator that you should absolutely *not* include
it in a driver.
>
> #include "amdgpu.h"
> #include "amdgpu_pm.h"
> @@ -2600,6 +2602,35 @@ static const struct drm_crtc_helper_funcs dce_v6_0_crtc_helper_funcs = {
> .get_scanout_position = amdgpu_crtc_get_scanout_position,
> };
>
> +static int dce_v6_0_drm_primary_plane_get_scanout_buffer(struct drm_plane *plane,
> + struct drm_scanout_buffer *sb)
> +{
> + struct drm_framebuffer *fb;
> + struct drm_gem_object *obj;
> + struct amdgpu_bo *abo;
> + int ret = 0;
> +
> + if (!plane->fb || plane->fb->modifier != DRM_FORMAT_MOD_LINEAR)
> + return -ENODEV;
> +
> + fb = plane->fb;
> + sb->width = fb->width;
> + sb->height = fb->height;
> + sb->format = fb->format;
> + sb->pitch[0] = fb->pitches[0];
> +
> + obj = fb->obj[0];
> + abo = gem_to_amdgpu_bo(obj);
> + if (!abo || abo->flags & AMDGPU_GEM_CREATE_NO_CPU_ACCESS)
> + return -EINVAL;
> +
> + return drm_gem_vmap(obj, &sb->map[0]);
Yeah that will almost always not work. Most display buffers are tilled
and not CPU accessible.
Regards,
Christian.
> +}
> +
> +static const struct drm_plane_helper_funcs dce_v6_0_drm_primary_plane_helper_funcs = {
> + .get_scanout_buffer = dce_v6_0_drm_primary_plane_get_scanout_buffer
> +};
> +
> static int dce_v6_0_crtc_init(struct amdgpu_device *adev, int index)
> {
> struct amdgpu_crtc *amdgpu_crtc;
> @@ -2627,6 +2658,7 @@ static int dce_v6_0_crtc_init(struct amdgpu_device *adev, int index)
> amdgpu_crtc->encoder = NULL;
> amdgpu_crtc->connector = NULL;
> drm_crtc_helper_add(&amdgpu_crtc->base, &dce_v6_0_crtc_helper_funcs);
> + drm_plane_helper_add(amdgpu_crtc->base.primary, &dce_v6_0_drm_primary_plane_helper_funcs);
>
> return 0;
> }
next prev parent reply other threads:[~2024-08-02 9:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 7:17 Lu Yao
2024-08-02 9:39 ` Christian König [this message]
2024-08-05 2:14 ` yaolu
2024-08-05 9:25 ` Jocelyn Falempe
2024-08-08 6:15 ` Lu Yao
2024-08-08 16:43 ` Alex Deucher
2024-08-08 17:24 ` Alex Deucher
2024-08-12 2:10 ` Lu Yao
2024-08-12 6:09 ` [PATCH v2] " Lu Yao
2024-09-17 12:25 ` Jocelyn Falempe
2024-09-17 13:21 ` Alex Deucher
2024-09-18 6:04 ` Lu Yao
2024-09-20 15:36 ` Jocelyn Falempe
2024-09-24 14:02 ` Alex Deucher
2024-09-25 7:55 ` Michel Dänzer
2024-09-25 8:33 ` Jocelyn Falempe
2024-10-01 12:43 ` Jocelyn Falempe
2024-10-29 14:28 ` Alex Deucher
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=ce45d800-ad6a-4cef-9c57-480908867490@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=Xinhui.Pan@amd.com \
--cc=airlied@gmail.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivasan.shanmugam@amd.com \
--cc=sunil.khatri@amd.com \
--cc=yaolu@kylinos.cn \
/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
all inboxes | Powered by JetHome®