From: Thomas Zimmermann <tzimmermann@suse.de>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Javier Martinez Canillas <javierm@redhat.com>
Cc: Peng Fan <peng.fan@nxp.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/fbdev-dma: fix getting smem_start
Date: Wed, 12 Jun 2024 08:48:32 +0200 [thread overview]
Message-ID: <e307fdc0-553d-4946-9017-ed3a28e9cae2@suse.de> (raw)
In-Reply-To: <8f4a6d80-dd3e-422f-88af-d26f50c973ff@suse.de>
Hi
Am 10.06.24 um 10:47 schrieb Thomas Zimmermann:
> Hi
>
> Am 04.06.24 um 10:03 schrieb Peng Fan (OSS):
>> From: Peng Fan <peng.fan@nxp.com>
>>
>> If 'info->screen_buffer' locates in vmalloc address space, virt_to_page
>> will not be able to get correct results. With CONFIG_DEBUG_VM and
>> CONFIG_DEBUG_VIRTUAL enabled on ARM64, there is dump below:
>
> Which graphics driver triggers this bug?
>
>> [ 3.536043] ------------[ cut here ]------------
>> [ 3.540716] virt_to_phys used for non-linear address:
>> 000000007fc4f540 (0xffff800086001000)
>> [ 3.552628] WARNING: CPU: 4 PID: 61 at arch/arm64/mm/physaddr.c:12
>> __virt_to_phys+0x68/0x98
>> [ 3.565455] Modules linked in:
>> [ 3.568525] CPU: 4 PID: 61 Comm: kworker/u12:5 Not tainted
>> 6.6.23-06226-g4986cc3e1b75-dirty #250
>> [ 3.577310] Hardware name: NXP i.MX95 19X19 board (DT)
>> [ 3.582452] Workqueue: events_unbound deferred_probe_work_func
>> [ 3.588291] pstate: 60400009 (nZCv daif +PAN -UAO -TCO -DIT -SSBS
>> BTYPE=--)
>> [ 3.595233] pc : __virt_to_phys+0x68/0x98
>> [ 3.599246] lr : __virt_to_phys+0x68/0x98
>> [ 3.603276] sp : ffff800083603990
>> [ 3.677939] Call trace:
>> [ 3.680393] __virt_to_phys+0x68/0x98
>> [ 3.684067] drm_fbdev_dma_helper_fb_probe+0x138/0x238
>> [ 3.689214] __drm_fb_helper_initial_config_and_unlock+0x2b0/0x4c0
>> [ 3.695385] drm_fb_helper_initial_config+0x4c/0x68
>> [ 3.700264] drm_fbdev_dma_client_hotplug+0x8c/0xe0
>> [ 3.705161] drm_client_register+0x60/0xb0
>> [ 3.709269] drm_fbdev_dma_setup+0x94/0x148
>>
>> So add a check 'is_vmalloc_addr'.
>>
>> Fixes: b79fe9abd58b ("drm/fbdev-dma: Implement fbdev emulation for
>> GEM DMA helpers")
>> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>
> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
I'm taking back my r-b. The memory is expected to by be physically
contiguous and vmalloc() won't guarantee that.
Best regards
Thomas
>
> Best regards
> Thomas
>
>> ---
>> drivers/gpu/drm/drm_fbdev_dma.c | 7 ++++++-
>> 1 file changed, 6 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_fbdev_dma.c
>> b/drivers/gpu/drm/drm_fbdev_dma.c
>> index 6c9427bb4053..9e2eddb6eb5c 100644
>> --- a/drivers/gpu/drm/drm_fbdev_dma.c
>> +++ b/drivers/gpu/drm/drm_fbdev_dma.c
>> @@ -130,7 +130,12 @@ static int drm_fbdev_dma_helper_fb_probe(struct
>> drm_fb_helper *fb_helper,
>> info->flags |= FBINFO_READS_FAST; /* signal caching */
>> info->screen_size = sizes->surface_height * fb->pitches[0];
>> info->screen_buffer = map.vaddr;
>> - info->fix.smem_start =
>> page_to_phys(virt_to_page(info->screen_buffer));
>> +
>> + if (is_vmalloc_addr(info->screen_buffer))
>> + info->fix.smem_start =
>> page_to_phys(vmalloc_to_page(info->screen_buffer));
>> + else
>> + info->fix.smem_start =
>> page_to_phys(virt_to_page(info->screen_buffer));
>> +
>> info->fix.smem_len = info->screen_size;
>> return 0;
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
next prev parent reply other threads:[~2024-06-12 6:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 8:03 [PATCH] drm/fbdev-dma: fix getting smem_start Peng Fan (OSS)
2024-06-10 8:47 ` Thomas Zimmermann
2024-06-11 1:00 ` Peng Fan
2024-06-11 7:50 ` Thomas Zimmermann
2024-06-11 8:23 ` Peng Fan
2024-06-11 9:29 ` Thomas Zimmermann
2024-06-12 8:45 ` Daniel Vetter
2024-06-12 13:03 ` Thomas Zimmermann
2024-06-12 6:48 ` Thomas Zimmermann [this message]
2024-06-12 7:49 ` Javier Martinez Canillas
2024-06-12 8:37 ` Thomas Zimmermann
2024-06-12 15:00 ` Daniel Vetter
2024-06-13 10:14 ` Thomas Zimmermann
2024-06-13 10:18 ` Thomas Zimmermann
2024-06-17 14:04 ` Daniel Vetter
2024-06-17 14:26 ` Thomas Zimmermann
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=e307fdc0-553d-4946-9017-ed3a28e9cae2@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox