From: "Arnd Bergmann" <arnd@arndb.de>
To: "Christian König" <christian.koenig@amd.com>,
"Randy Dunlap" <rdunlap@infradead.org>,
"Arnd Bergmann" <arnd@kernel.org>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>
Cc: "Dave Airlie" <airlied@gmail.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
"Arunpravin Paneer Selvam" <Arunpravin.PaneerSelvam@amd.com>,
"David Gow" <davidgow@google.com>,
"Maíra Canal" <mcanal@igalia.com>,
"Matthew Auld" <matthew.auld@intel.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/tests/drm_buddy: avoid 64-bit calculation
Date: Mon, 19 Feb 2024 12:29:57 +0100 [thread overview]
Message-ID: <fbd0426c-fdd2-4b7f-a13e-072ed5f973de@app.fastmail.com> (raw)
In-Reply-To: <4cdc5b58-11c1-490d-8c3b-6352d8f1b8cb@amd.com>
On Mon, Feb 19, 2024, at 12:22, Christian König wrote:
> Am 17.02.24 um 02:31 schrieb Randy Dunlap:
>> On 2/16/24 12:24, Arnd Bergmann wrote:
>>> From: Arnd Bergmann <arnd@arndb.de>
>>>
>>> The newly added drm_test_buddy_alloc_contiguous() test fails to link on
>>> 32-bit targets because of inadvertent 64-bit calculations:
>>>
>>> ERROR: modpost: "__aeabi_uldivmod" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
>>> ERROR: modpost: "__aeabi_ldivmod" [drivers/gpu/drm/tests/drm_buddy_test.ko] undefined!
>>>
>>> >From what I can tell, the numbers cannot possibly overflow a 32-bit size,
>>> so use different types for these.
>>>
>>> I noticed that the function has another possible flaw in that is mixes
>>> what it calls pages with 4KB units. This is a big confusing at best,
>>> or possibly broken when built on machines with larger pages.
>>>
>>> Fixes: a64056bb5a32 ("drm/tests/drm_buddy: add alloc_contiguous test")
>>> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
>> Tested-by: Randy Dunlap <rdunlap@infradead.org>
>
> I've just pushed a similar patch Mathew came up a bit earlier to
> drm-misc-fixes.
>
> Sorry for the noise, I have to catch up on picking up patches for
> misc-fixes and misc-next.
Ok, thanks.
Have you looked at how this code works for larger values of PAGE_SIZE?
Is there any need to change other things or will this work with the
hardcoded 4KB chunks?
Arnd
next prev parent reply other threads:[~2024-02-19 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 20:24 Arnd Bergmann
2024-02-17 1:31 ` Randy Dunlap
2024-02-19 11:22 ` Christian König
2024-02-19 11:29 ` Arnd Bergmann [this message]
2024-02-19 11:41 ` Christian König
2024-02-19 11:49 ` Matthew Auld
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=fbd0426c-fdd2-4b7f-a13e-072ed5f973de@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=airlied@gmail.com \
--cc=arnd@kernel.org \
--cc=christian.koenig@amd.com \
--cc=daniel@ffwll.ch \
--cc=davidgow@google.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=matthew.auld@intel.com \
--cc=mcanal@igalia.com \
--cc=mripard@kernel.org \
--cc=rdunlap@infradead.org \
--cc=tzimmermann@suse.de \
/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®