From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Remaining passthrough/VT-d tasks list Date: Wed, 24 Sep 2008 11:53:15 +0300 Message-ID: <48D9FFFB.5040505@redhat.com> References: <0122C7C995D32147B66BF4F440D3016301C49E61@pdsmsx415.ccr.corp.intel.com> <48D9FB8E.9060505@redhat.com> <200809241642.54667.sheng.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "Han, Weidong" , "kvm@vger.kernel.org" , Amit Shah , "benami@il.ibm.com" , "muli@il.ibm.com" , "Kay, Allen M" , "Zhang, Xiantao" To: "Yang, Sheng" Return-path: Received: from mx2.redhat.com ([66.187.237.31]:50365 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751437AbYIXIyy (ORCPT ); Wed, 24 Sep 2008 04:54:54 -0400 In-Reply-To: <200809241642.54667.sheng.yang@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Yang, Sheng wrote: >> Shared guest interrupts is a prerequisite for merging into mainline. >> Without this, device assignment is useless in anything but a benchmark >> scenario. I won't push device assignment for 2.6.28 without it. >> >> Shared host interrupts are a different matter; which one did you mean? >> >> > > Got confused... > > I think we are talking about share host interrupts, that is pre-assigned > device shared IRQ with other devices. > > Why share guest interrupts is a prerequisite... > We only have three pci interrupts at this point (though this could be easily extended); if you start the guest with a non-trivial number of devices, you will have shared guest interrupts. (of course, when I pointed this out during review, people said it could be done later, then forgot all about it) -- error compiling committee.c: too many arguments to function