[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem


  • To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
  • From: Bruce Edge <bruce.edge@xxxxxxxxx>
  • Date: Fri, 8 Oct 2010 10:52:26 -0700
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Lin, Ray" <Ray.Lin@xxxxxxx>
  • Delivery-date: Fri, 08 Oct 2010 10:53:08 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=QlIsHg22RaxLn3fwqSP0HruZg9Afhic033Zxj/ZAeAgJhHSi2qmVOQ8gcoI+dxxa+Y PD5MlzI1owVxFB8cau92qDlsK6ePfN3xfB8UpxVlwI8CHG2gEOldlPXdEoMTuAVINka/ 9HDLdVuP7nB3JBBuy2tzzj0r25mq8MDXwinUw=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Fri, Oct 8, 2010 at 10:30 AM, Konrad Rzeszutek Wilk
<konrad.wilk@xxxxxxxxxx> wrote:
> 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
>>
>

The above was from xen-testing, I just switched Ray over to
xen-unstable. He's re-running now with the later hypervisor.

-Bruce

> And you still get on the Xen hypervisor side the DMAR failure of reading the 
> memory?
>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.