From: Paul Bolle <pebolle@tiscali.nl>
To: David Airlie <airlied@linux.ie>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/vmwgfx: use *_32_bits() macros
Date: Thu, 14 Apr 2016 13:32:20 +0200 [thread overview]
Message-ID: <1460633540.2728.6.camel@tiscali.nl> (raw)
In-Reply-To: <1457000770-2317-1-git-send-email-pebolle@tiscali.nl>
On do, 2016-03-03 at 11:26 +0100, Paul Bolle wrote:
> Use the upper_32_bits() macro instead of the four line equivalent that
> triggers a GCC warning on 32 bits x86:
> drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c: In function
> 'vmw_cmdbuf_header_submit':
> drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c:297:25: warning: right
> shift count >= width of type [-Wshift-count-overflow]
> val = (header->handle >> 32);
> ^
>
> And use the lower_32_bits() macro instead of and-ing with a 32 bits
> mask.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
> ---
> Note: compile tested only (I don't use any of vmware's products).
The warning can still be seen on v4.6-rc3 for 32 bits x86. This patch
applies cleanly to that rc.
Has anyone had a chance to look at this patch, and perhaps even test it?
Thanks,
Paul Bolle
> drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c | 7 ++-----
> 1 file changed, 2 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c
> b/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c
> index 67cebb23c940..aa04fb0159a7 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_cmdbuf.c
> @@ -293,13 +293,10 @@ static int vmw_cmdbuf_header_submit(struct
> vmw_cmdbuf_header *header)
> struct vmw_cmdbuf_man *man = header->man;
> u32 val;
>
> - if (sizeof(header->handle) > 4)
> - val = (header->handle >> 32);
> - else
> - val = 0;
> + val = upper_32_bits(header->handle);
> vmw_write(man->dev_priv, SVGA_REG_COMMAND_HIGH, val);
>
> - val = (header->handle & 0xFFFFFFFFULL);
> + val = lower_32_bits(header->handle);
> val |= header->cb_context & SVGA_CB_CONTEXT_MASK;
> vmw_write(man->dev_priv, SVGA_REG_COMMAND_LOW, val);
>
next prev parent reply other threads:[~2016-04-14 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 10:26 [PATCH] drm/vmwgfx: use *_32_bits() macros Paul Bolle
2016-04-14 11:32 ` Paul Bolle [this message]
2016-04-14 14:34 ` Joe Perches
2016-06-15 8:37 ` Paul Bolle
2016-06-15 11:11 ` Daniel Vetter
2016-06-15 11:59 ` Thomas Hellstrom
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=1460633540.2728.6.camel@tiscali.nl \
--to=pebolle@tiscali.nl \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
/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