linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Robert Richter <robert.richter@caviumnetworks.com>
Cc: Robert Richter <rric@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Jason Cooper <jason@lakedaemon.net>,
	Marc Zyngier <marc.zyngier@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] GICv3: Fixing 32 bit compatibility
Date: Tue, 9 Sep 2014 11:43:39 +0200	[thread overview]
Message-ID: <20140909094339.GR23009@pengutronix.de> (raw)
In-Reply-To: <20140909092653.GC4588@rric.localhost>

On Tue, Sep 09, 2014 at 11:26:53AM +0200, Robert Richter wrote:
> On 09.09.14 11:19:12, Uwe Kleine-König wrote:
> > On Tue, Sep 09, 2014 at 11:12:01AM +0200, Robert Richter wrote:
> > > On 09.09.14 10:00:42, Uwe Kleine-König wrote:
> > > > On Mon, Sep 08, 2014 at 04:11:19PM +0200, Robert Richter wrote:
> > > 
> > > > > @@ -479,7 +479,7 @@ static void gic_raise_softirq(const struct cpumask *mask, unsigned int irq)
> > > > >     smp_wmb();
> > > > >  
> > > > >     for_each_cpu_mask(cpu, *mask) {
> > > > > -           u64 cluster_id = cpu_logical_map(cpu) & ~0xffUL;
> > > > > +           u64 cluster_id = cpu_logical_map(cpu) & ~0xffULL;
> > > > This doesn't change anything, does it?
> > > 
> > > It does, not in 64 bit but in 32 bit there unsigned long is 32
> > > bit. So, bit masks are broken if you compile a 32 bit kernel.
> > Can you make an example where the result actually changes?
> 
> Upper 32 bits will be cleared above.
ah, I missed the ~ while thinking about the difference.

> > > > I wonder if it would be cleaner to use (u64)0xff here.
> > > 
> > > No, that's ULL for. This is commonly used in x86 too.
> > I don't care much here, but I'd say ULL is to force an unsigned long
> > long. If you want to make it obvious that you want a 64bit value, a cast
> > to u64 makes this more clear.
> 
> ULL is no cast at all.
That's irrelevant here if it's a cast or not. It makes the constant be
an unsigned long long one.

If you want an unsigned long long value, use ULL (or a cast to unsigned
long long if the value permits), if you want an u64 use a cast to u64.

Probably it doesn't make sense to continue to argue here. The type of
cpu_logical_map(cpu) varies per architecture but is always <= 64 bits
wide and IIRC unsigned long long is guaranteed to be >= 64 bits wide so
everything is fine with your patch today.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

      reply	other threads:[~2014-09-09  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-08 14:11 [PATCH] GICv3: Fixing 32 bit compatibility Robert Richter
2014-09-08 14:24 ` Marc Zyngier
2014-09-14  5:55   ` Jason Cooper
2014-09-08 14:31 ` [PATCH] ITS: " Robert Richter
2014-09-09  8:00 ` [PATCH] GICv3: " Uwe Kleine-König
2014-09-09  9:12   ` Robert Richter
2014-09-09  9:19     ` Uwe Kleine-König
2014-09-09  9:26       ` Robert Richter
2014-09-09  9:43         ` Uwe Kleine-König [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=20140909094339.GR23009@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=robert.richter@caviumnetworks.com \
    --cc=rric@kernel.org \
    --cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).