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

["Lin, Ray" <Ray.Lin@xxxxxxx>]

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


-Ray

-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx 
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Bruce Edge
Sent: Wednesday, October 06, 2010 11:21 AM
To: Konrad Rzeszutek Wilk
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] pv-ops domU not working with MSI interrupts on Nehalem

On Wed, Oct 6, 2010 at 7:21 AM, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> 
wrote:
> On Tue, Oct 05, 2010 at 11:21:38AM -0700, Bruce Edge wrote:
>> On Mon, Oct 4, 2010 at 7:48 AM, Konrad Rzeszutek Wilk 
>> <konrad.wilk@xxxxxxxxxx> wrote:
>> >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git ?
>> >>
>> >> Your devel/xen-pcifront-0.7 isn't visible:
>> >
>> > It should be now. I pushed it late on Friday and repushed it today 
>> > since it had some commits with the wrong committer field.
>> >
>>
>> Is there anything special one needs to do when building this kernel?
>
> Wow. I've never seen those errors before. Can you send me your .config 
> file so I can make sure this does not happend

Those errors were from after a 'make defconfig'. I assumed my config was broken 
and that I should try the default .config to confirm that that built before 
digging thought mine.

Adding the config entries below to the defconfig output does result in a 
buildable kernel.

Testing out my PCI drivers with your recommended config now. Thanks.

-Bruce

>
> For me, I've these options defined:
>
> [konrad@tst002 bootstrap]$ cat linux-build/.config|grep XEN 
> CONFIG_XEN=y CONFIG_XEN_PVHVM=y
> CONFIG_XEN_MAX_DOMAIN_MEMORY=8
> CONFIG_XEN_SAVE_RESTORE=y
> CONFIG_XEN_DEBUG_FS=y
> CONFIG_PCI_XEN=y
> CONFIG_XEN_PCIDEV_FRONTEND=y
> CONFIG_XEN_BLKDEV_FRONTEND=m
> # CONFIG_NETXEN_NIC is not set
> CONFIG_XEN_NETDEV_FRONTEND=m
> CONFIG_XEN_KBDDEV_FRONTEND=m
> CONFIG_HVC_XEN=y
> CONFIG_XEN_FBDEV_FRONTEND=m
> CONFIG_XEN_BALLOON=y
> CONFIG_XEN_SCRUB_PAGES=y
> CONFIG_XEN_DEV_EVTCHN=m
> CONFIG_XENFS=m
> CONFIG_XEN_COMPAT_XENFS=y
> CONFIG_XEN_SYS_HYPERVISOR=y
> CONFIG_XEN_PLATFORM_PCI=m
> CONFIG_SWIOTLB_XEN=y
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel