From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 09/10] KVM: Enable MSI for device assignment Date: Tue, 04 Nov 2008 17:01:04 +0200 Message-ID: <491063B0.9030302@redhat.com> References: <1225428647-27614-1-git-send-email-sheng@linux.intel.com> <1225428647-27614-10-git-send-email-sheng@linux.intel.com> <49103098.7020109@redhat.com> <20081104132543.GB18696@yukikaze> <49104F01.30604@redhat.com> <20081104135853.GC18696@yukikaze> <49105DA7.3020204@redhat.com> <20081104145716.GD18696@yukikaze> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit To: Avi Kivity , Sheng Yang , kvm@vger.kernel.org Return-path: Received: from mx2.redhat.com ([66.187.237.31]:52582 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752326AbYKDPBJ (ORCPT ); Tue, 4 Nov 2008 10:01:09 -0500 In-Reply-To: <20081104145716.GD18696@yukikaze> Sender: kvm-owner@vger.kernel.org List-ID: Sheng Yang wrote: >> struct gsi { >> u32 n : 24; >> u32 type : 8; // 0 -> classic gsi, 1 -> msi >> }; >> > > I just don't understand why we need 24 bits for n? GSI can be that wide? > I don't think so, but who knows what we'll need for type == 2? -- error compiling committee.c: too many arguments to function