From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Wed, 16 Jan 2013 09:44:44 +0000 Subject: [PATCH v5 03/14] KVM: ARM: Initial skeleton to compile KVM support In-Reply-To: <877gndzvi6.fsf@rustcorp.com.au> References: <20130108183811.46302.58543.stgit@ubuntu> <20130108183855.46302.40539.stgit@ubuntu> <20130114162415.GF23505@n2100.arm.linux.org.uk> <877gndzvi6.fsf@rustcorp.com.au> Message-ID: <20130116094444.GP23505@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Wed, Jan 16, 2013 at 01:26:01PM +1030, Rusty Russell wrote: > Christoffer Dall writes: > > > On Mon, Jan 14, 2013 at 11:24 AM, Russell King - ARM Linux > > wrote: > >> On Tue, Jan 08, 2013 at 01:38:55PM -0500, Christoffer Dall wrote: > >>> + /* -ENOENT for unknown features, -EINVAL for invalid combinations. */ > >>> + for (i = 0; i < sizeof(init->features)*8; i++) { > >>> + if (init->features[i / 32] & (1 << (i % 32))) { > >> > >> Isn't this an open-coded version of test_bit() ? > > > > indeed, nicely spotted: > > BTW, I wrote it that was out of excessive paranoia: it's a userspace > API, and test_bit() won't be right on 64 bit BE systems. So why is this a concern for 32-bit systems (which are, by definition, only in arch/arm) ?