From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sheng Yang Subject: Re: KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY should support MSI? Date: Wed, 20 May 2009 16:48:17 +0800 Message-ID: <200905201648.18249.sheng@linux.intel.com> References: <20090505103028.GA15418@redhat.com> <4A00230A.70607@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: Gregory Haskins , "Michael S. Tsirkin" , Avi Kivity , Marcelo Tosatti , Matthew Wilcox To: kvm@vger.kernel.org Return-path: Received: from mga05.intel.com ([192.55.52.89]:20250 "EHLO fmsmga101.fm.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752811AbZETIrZ (ORCPT ); Wed, 20 May 2009 04:47:25 -0400 In-Reply-To: <4A00230A.70607@gmail.com> Content-Disposition: inline Sender: kvm-owner@vger.kernel.org List-ID: On Tuesday 05 May 2009 19:29:14 Gregory Haskins wrote: > Michael S. Tsirkin wrote: > > The new KVM_ASSIGN_SET_MSIX_NR and KVM_ASSIGN_SET_MSIX_ENTRY ioctls have > > been merged for 2.6.30. However, I note that PCI spec allows devices to > > support multiple vectors with MSI as well (support will be in linux > > 2.6.30). > > > > Even though qemu for now only uses a single vector with MSI, it would > > seem that it's better to make the kernel/user interface generic straight > > away rather than add more ioctls later. What do you think? It might not > > be too late to fix this for 2.6.30. > > +1 Hi Sorry for I don't have time to work at it recently... And Avi's review patchset reminded me the merge for 2.6.31 would be soon. Anyone have interesting to get this done? Thanks! -- regards Yang, Sheng