From: Daniel Thompson <daniel.thompson@linaro.org>
To: Ilia Mirkin <imirkin@alum.mit.edu>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: linux-fbdev@vger.kernel.org,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Ben Skeggs <bskeggs@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: likely signedness bug in drm and nvidia drivers
Date: Tue, 21 Jul 2015 08:56:07 +0000 [thread overview]
Message-ID: <55AE0927.1060604@linaro.org> (raw)
In-Reply-To: <CAKb7UvhLp=G6yH7MgivOPp9kDDdH2Y2q4v0YDjt8vHewLzzy=w@mail.gmail.com>
On 21/07/15 03:44, Ilia Mirkin wrote:
> I think you're right. The intent is to mask off the bits above>
bits_per_pixel. So if bits_per_pixel is 24, the mask would be>
0xff000000. If it's 16, then the mask would be 0xffff0000. If it's 32,>
then the mask is 0.> > In reality, bits_per_pixel is almost exclusively
32, which will end up> with a mask of 0 (note that the shift result is
inverted at the end).> So for the majority case, there's not bug... just
a useless operation.> > I took a look at linux/bitops.h, and there's
nothing particularly> great there. GENMASK, I guess, but it's not quite
right. Just> switching to 0U should be fine there.
I really don't see GENMASK() isn't quite right.
Try:
uint32_t mask = GENMASK(32, info->var.bits_per_pixel);
Versus:
uint32_t mask = ~(~0u >> (32 - info->var.bits_per_pixel));
For me, the GENMASK() is obvious whilst the later takes a good bit of
mental decoding.
Daniel.
prev parent reply other threads:[~2015-07-21 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 20:46 likely signedness bug in drm and nvidia drivers Rasmus Villemoes
2015-07-21 2:44 ` Ilia Mirkin
2015-07-21 8:56 ` Daniel Thompson [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=55AE0927.1060604@linaro.org \
--to=daniel.thompson@linaro.org \
--cc=bskeggs@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=imirkin@alum.mit.edu \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=tomi.valkeinen@ti.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;
as well as URLs for NNTP newsgroup(s).