From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v2 4/6] kvm: Extend irqfd to support level interrupts Date: Thu, 28 Jun 2012 15:41:33 +0300 Message-ID: <4FEC50FD.6030402@redhat.com> References: <20120627044758.23698.249.stgit@bling.home> <20120627050937.23698.68442.stgit@bling.home> <20120627093427.GE17507@redhat.com> <1340831986.1207.250.camel@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: "Michael S. Tsirkin" , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, jan.kiszka@siemens.com To: Alex Williamson Return-path: In-Reply-To: <1340831986.1207.250.camel@bling.home> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 06/28/2012 12:19 AM, Alex Williamson wrote: >> > @@ -302,6 +385,7 @@ kvm_irqfd_deassign(struct kvm *kvm, struct kvm_irqfd *args) >> > { >> > struct _irqfd *irqfd, *tmp; >> > struct eventfd_ctx *eventfd; >> > + bool is_level = (args->flags & KVM_IRQFD_FLAG_LEVEL) != 0; >> >> != 0 is not needed here I think. > > Strictly, no it's not. I just prefer to set bools from bools and I > think Avi has commented on using !! before. I prefer the naked version too, but != 0 is acceptable. -- error compiling committee.c: too many arguments to function