From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cornelia Huck Subject: Re: [PATCH 1/5] KVM: change API for requests to match bit operations Date: Fri, 17 Feb 2017 10:52:53 +0100 Message-ID: <20170217105253.12ce475d.cornelia.huck@de.ibm.com> References: <20170216160449.13094-1-rkrcmar@redhat.com> <20170216160449.13094-2-rkrcmar@redhat.com> <20170217103014.5ada1f1c.cornelia.huck@de.ibm.com> <20170217094935.u7ne57y7ko6h2mnz@kamzik.brq.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Cc: Radim =?UTF-8?B?S3LEjW3DocWZ?= , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Paolo Bonzini , Marc Zyngier , Christian Borntraeger , James Hogan , Paul Mackerras , Christoffer Dall To: Andrew Jones Return-path: In-Reply-To: <20170217094935.u7ne57y7ko6h2mnz@kamzik.brq.redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Fri, 17 Feb 2017 10:49:35 +0100 Andrew Jones wrote: > On Fri, Feb 17, 2017 at 10:30:14AM +0100, Cornelia Huck wrote: > > On Thu, 16 Feb 2017 17:04:45 +0100 > > Radim Krčmář wrote: > > > +static inline void kvm_request_set(unsigned req, struct kvm_vcpu *vcpu) > > > > Should we make req unsigned long as well, so that it matches the bit > > api even more? > > The bitops API is inconsistent among architectures; some are int, some > are unsigned int, some are unsigned long, and x86 is long. If we want > to be consistent with something, then, IMO, we should be consistent with > asm-generic/bitops, which is int, but actually unsigned makes more sense > to me... Inconsistent interfaces are great :/ Having (any) unsigned value makes the most sense to me as well.