From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: pv-ops domU not working with MSI interrupts on Nehalem Date: Fri, 8 Oct 2010 13:30:54 -0400 Message-ID: <20101008173054.GA20884@dumpdata.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Lin, Ray" Cc: "xen-devel@lists.xensource.com" , Bruce Edge List-Id: xen-devel@lists.xenproject.org On Fri, Oct 08, 2010 at 10:48:01AM -0600, Lin, Ray wrote: > > I just tried Bruce's latest kernel build based on Konrad's devel/xen-pcifront-0.7. It doesn't help the issue we have. The driver still doesn't recognize the source of interrupt, even though the interrupts happen. > > > 124: 87792 0 0 0 0 0 12208 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON > 125: 89692 0 0 0 10308 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON > 126: 90979 0 9021 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON > 127: 100000 0 0 0 0 0 0 0 0 0 0 0 0 0 xen-pirq-pcifront-msi HW_TACHYON > And you still get on the Xen hypervisor side the DMAR failure of reading the memory?