From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Arun R Murthy <arun.r.murthy@intel.com>
Cc: <intel-gfx@lists.freedesktop.org>,
<intel-xe@lists.freedesktop.org>, <ville.syrjala@intel.com>
Subject: Re: [PATCHv3] drm/xe/display: use mul_u32_u32 for multiplying operands
Date: Wed, 24 Apr 2024 16:11:41 -0400 [thread overview]
Message-ID: <ZilnfeAdsh4eh-3h@intel.com> (raw)
In-Reply-To: <20240410024810.1707500-1-arun.r.murthy@intel.com>
On Wed, Apr 10, 2024 at 08:18:10AM +0530, Arun R Murthy wrote:
> Use mul_u32_u32 to avoid potential overflow in multiplying two u32 and
> store the u64 result.
>
> v2: remove u64 typecast and use mul_u32_u32 (Ville)
> v3: Reframe the commit message <Rodrigo>
I still believe that the message is not that clear tbh.
I mean, just by reading that without the understanding of the flow,
one might simply ask, how can you overflow a 64bit with a u32 times u32?
I was going to tweak that while pushing, but I got a conflict.
So it needs a rebase anyway, so probably making sure that it is
clear that compiler can use a u32 for storing the multiplication
before it moves the result to the u64 and that could overflow.
So, this cast forces the compiler to already use a u64 during
the multiplication, before the final store.
>
> Signed-off-by: Arun R Murthy <arun.r.murthy@intel.com>
> ---
> drivers/gpu/drm/xe/display/xe_fb_pin.c | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/display/xe_fb_pin.c b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> index 3a584bc3a0a3..c73054c09ae9 100644
> --- a/drivers/gpu/drm/xe/display/xe_fb_pin.c
> +++ b/drivers/gpu/drm/xe/display/xe_fb_pin.c
> @@ -29,7 +29,7 @@ write_dpt_rotated(struct xe_bo *bo, struct iosys_map *map, u32 *dpt_ofs, u32 bo_
> u32 src_idx = src_stride * (height - 1) + column + bo_ofs;
>
> for (row = 0; row < height; row++) {
> - u64 pte = ggtt->pt_ops->pte_encode_bo(bo, src_idx * XE_PAGE_SIZE,
> + u64 pte = ggtt->pt_ops->pte_encode_bo(bo, mul_u32_u32(src_idx, XE_PAGE_SIZE),
> xe->pat.idx[XE_CACHE_NONE]);
>
> iosys_map_wr(map, *dpt_ofs, u64, pte);
> @@ -61,8 +61,8 @@ write_dpt_remapped(struct xe_bo *bo, struct iosys_map *map, u32 *dpt_ofs,
>
> for (column = 0; column < width; column++) {
> iosys_map_wr(map, *dpt_ofs, u64,
> - pte_encode_bo(bo, src_idx * XE_PAGE_SIZE,
> - xe->pat.idx[XE_CACHE_NONE]));
> + pte_encode_bo(bo, mul_u32_u32(src_idx, XE_PAGE_SIZE),
> + xe->pat.idx[XE_CACHE_NONE]));
>
> *dpt_ofs += 8;
> src_idx++;
> @@ -121,7 +121,7 @@ static int __xe_pin_fb_vma_dpt(struct intel_framebuffer *fb,
> u32 x;
>
> for (x = 0; x < size / XE_PAGE_SIZE; x++) {
> - u64 pte = ggtt->pt_ops->pte_encode_bo(bo, x * XE_PAGE_SIZE,
> + u64 pte = ggtt->pt_ops->pte_encode_bo(bo, mul_u32_u32(x, XE_PAGE_SIZE),
> xe->pat.idx[XE_CACHE_NONE]);
>
> iosys_map_wr(&dpt->vmap, x * 8, u64, pte);
> @@ -167,7 +167,7 @@ write_ggtt_rotated(struct xe_bo *bo, struct xe_ggtt *ggtt, u32 *ggtt_ofs, u32 bo
> u32 src_idx = src_stride * (height - 1) + column + bo_ofs;
>
> for (row = 0; row < height; row++) {
> - u64 pte = ggtt->pt_ops->pte_encode_bo(bo, src_idx * XE_PAGE_SIZE,
> + u64 pte = ggtt->pt_ops->pte_encode_bo(bo, mul_u32_u32(src_idx, XE_PAGE_SIZE),
> xe->pat.idx[XE_CACHE_NONE]);
>
> xe_ggtt_set_pte(ggtt, *ggtt_ofs, pte);
> --
> 2.25.1
>
prev parent reply other threads:[~2024-04-24 20:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 2:48 [PATCHv3] drm/xe/display: use mul_u32_u32 for multiplying operands Arun R Murthy
2024-04-10 3:09 ` ✓ CI.Patch_applied: success for " Patchwork
2024-04-10 3:10 ` ✗ CI.checkpatch: warning " Patchwork
2024-04-10 3:11 ` ✓ CI.KUnit: success " Patchwork
2024-04-10 3:23 ` ✓ CI.Build: " Patchwork
2024-04-10 3:26 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2024-04-10 3:27 ` ✓ CI.Hooks: success " Patchwork
2024-04-10 3:31 ` ✓ Fi.CI.BAT: " Patchwork
2024-04-10 3:32 ` ✓ CI.checksparse: " Patchwork
2024-04-10 4:01 ` ✓ CI.BAT: " Patchwork
2024-04-10 5:04 ` ✗ CI.FULL: failure " Patchwork
2024-04-10 20:31 ` ✗ Fi.CI.IGT: " Patchwork
2024-04-24 20:11 ` Rodrigo Vivi [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=ZilnfeAdsh4eh-3h@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.