From: "Vivi, Rodrigo" <rodrigo.vivi@intel.com>
To: "linux@roeck-us.net" <linux@roeck-us.net>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "airlied@linux.ie" <airlied@linux.ie>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Auld, Matthew" <matthew.auld@intel.com>,
"Das, Nirmoy" <nirmoy.das@intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix 32-bit build
Date: Sun, 17 Jul 2022 18:49:12 +0000 [thread overview]
Message-ID: <7fdf804a29d05bcfe57200de0f1fe049bdb91016.camel@intel.com> (raw)
In-Reply-To: <20220717162046.710290-1-linux@roeck-us.net>
On Sun, 2022-07-17 at 09:20 -0700, Guenter Roeck wrote:
> Commit aff1e0b09b54 ("drm/i915/ttm: fix sg_table construction")
> introduces
> an additional parameter to i915_rsgt_from_mm_node(). The parameter is
> used
> to calculate segment_pages. This in turn is used in DIV_ROUND_UP() as
> divisor. So far segment_pages was a constant and handled without
> divide
> operation. Since it is no longer constant, a divide operation is now
> necessary. This results in build errors on 32-bit builds.
>
> x86_64-linux-ld: drivers/gpu/drm/i915/i915_scatterlist.o:
> in function `i915_rsgt_from_mm_node':
> i915_scatterlist.c:(.text+0x196): undefined reference to `__udivdi3'
>
> Fix the problem by using DIV_ROUND_UP_ULL() instead of
> DIV_ROUND_UP().
>
> Fixes: aff1e0b09b54 ("drm/i915/ttm: fix sg_table construction")
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Nirmoy Das <nirmoy.das@intel.com>
> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> Signed-off-by: Guenter Roeck <linux@roeck-us.net>
> ---
> I took a stab at the problem. Please ignore the noise if it has
> already
> been fixed with a different patch.
Thanks for your patch.
This was actually fixed already in our -next branches, but missed
on the fixes:
https://patchwork.freedesktop.org/patch/493637/?series=106260&rev=1
Thanks,
Rodrigo.
>
> drivers/gpu/drm/i915/i915_scatterlist.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_scatterlist.c
> b/drivers/gpu/drm/i915/i915_scatterlist.c
> index f63b50b71e10..b81d5658c222 100644
> --- a/drivers/gpu/drm/i915/i915_scatterlist.c
> +++ b/drivers/gpu/drm/i915/i915_scatterlist.c
> @@ -96,7 +96,7 @@ struct i915_refct_sgt *i915_rsgt_from_mm_node(const
> struct drm_mm_node *node,
>
> i915_refct_sgt_init(rsgt, node->size << PAGE_SHIFT);
> st = &rsgt->table;
> - if (sg_alloc_table(st, DIV_ROUND_UP(node->size,
> segment_pages),
> + if (sg_alloc_table(st, DIV_ROUND_UP_ULL(node->size,
> segment_pages),
> GFP_KERNEL)) {
> i915_refct_sgt_put(rsgt);
> return ERR_PTR(-ENOMEM);
prev parent reply other threads:[~2022-07-17 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 16:20 [Intel-gfx] [PATCH] drm/i915: Fix 32-bit build Guenter Roeck
2022-07-17 16:35 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for " Patchwork
2022-07-17 16:52 ` Guenter Roeck
2022-07-17 17:00 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-17 18:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2022-07-17 18:49 ` Vivi, Rodrigo [this message]
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=7fdf804a29d05bcfe57200de0f1fe049bdb91016.camel@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@intel.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