From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: Remaining passthrough/VT-d tasks list Date: Sun, 05 Oct 2008 12:18:13 +0200 Message-ID: <48E89465.4060500@redhat.com> References: <0122C7C995D32147B66BF4F440D3016301C49E61@pdsmsx415.ccr.corp.intel.com> <48DF1046.1050102@redhat.com> <200809281317.53842.sheng.yang@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: 7bit Cc: "Tian, Kevin" , "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]:45277 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752967AbYJEKT3 (ORCPT ); Sun, 5 Oct 2008 06:19:29 -0400 In-Reply-To: <200809281317.53842.sheng.yang@intel.com> Sender: kvm-owner@vger.kernel.org List-ID: Yang, Sheng wrote: >> >> You're right, I didn't think it through. >> >> If there was a standard way to mask pci irqs, it might have worked, but >> there isn't, unfortunately. >> >> > What if we got a way to mask pci irqs? We also have to unmask pci irq when > guest wrote EOI to vlapic(or at any other time). I think this still cause > problem. The problem is, we don't know if guest would deassert the line. > Maybe add some time-based detection here might work? > > And about the mask of pci irq, how about disable PCI device interrupt using > Device Control Register bit 10? Not sure if it would affect the pending > transaction, also not sure all device support this (though they should > support). > I didn't know about this. I'll try to find a copy of the pci spec and read up on it. -- error compiling committee.c: too many arguments to function