From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [KVM PATCH v4 2/2] kvm: add support for irqfd via eventfd-notification interface Date: Tue, 05 May 2009 20:43:45 +0300 Message-ID: <4A007AD1.2020309@redhat.com> References: <20090504175657.26758.12503.stgit@dev.haskins.net> <20090504175750.26758.7023.stgit@dev.haskins.net> <4A005F05.30409@redhat.com> <4A0078B5.7030509@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, viro@ZenIV.linux.org.uk, linux-kernel@vger.kernel.org, davidel@xmailserver.org To: Gregory Haskins Return-path: Received: from mx2.redhat.com ([66.187.237.31]:44759 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752022AbZEERoV (ORCPT ); Tue, 5 May 2009 13:44:21 -0400 In-Reply-To: <4A0078B5.7030509@novell.com> Sender: kvm-owner@vger.kernel.org List-ID: Gregory Haskins wrote: >>> >>> +struct kvm_irqfd { >>> + __u32 gsi; >>> + __u32 flags; >>> +}; >>> + >>> >>> >> Please add some reserved space here. >> > > Ack. Any rule of thumb here? How about a "__u8 pad[16]" ? > I'd round it up so the whole thing is 32 bytes (not that it matters). -- Do not meddle in the internals of kernels, for they are subtle and quick to panic.