From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael S. Tsirkin" Subject: Re: [PATCH] KVM: Allow host IRQ sharing for assigned PCI 2.3 devices Date: Wed, 11 Jan 2012 11:47:13 +0200 Message-ID: <20120111094713.GB20988@redhat.com> References: <4F0AF394.6000205@siemens.com> <1326138346.1605.61.camel@bling.home> <4F0B5B49.2040305@web.de> <1326146754.1605.77.camel@bling.home> <4F0C4161.20403@siemens.com> <1326238910.22758.17.camel@bling.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jan Kiszka , Avi Kivity , Marcelo Tosatti , kvm , Jesse Barnes To: Alex Williamson Return-path: Received: from mx1.redhat.com ([209.132.183.28]:39754 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756616Ab2AKJpH (ORCPT ); Wed, 11 Jan 2012 04:45:07 -0500 Content-Disposition: inline In-Reply-To: <1326238910.22758.17.camel@bling.home> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Jan 10, 2012 at 04:41:50PM -0700, Alex Williamson wrote: > > The guest driver will never see such an interrupt as we will notice on > > its arrival that there is some mask pending. > > Right, I was thinking more about the affect at the hardware level. In theory a broken device might assume that intx disable bit is correlated with internal device registers somehow. However, the current sharing approach won't work for such a device anyway as host controls the status bit while guest controls the rest of the device. So I think we don't care. -- MST