From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Schiers Subject: AW: Re: Some test results on Xen 4.0 and 2.6.31 / 2.6.32 pvops kernels Date: Mon, 12 Apr 2010 15:01:33 +0200 Message-ID: <11672852.21271077293524.JavaMail.root@uhura> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel Cc: jeremy , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org Yet another note: the kernel messages that break 00:02.0 come up when I u= se 2.6.31 kernel, that means, if it is passing through the 00:02.1 into the pvops DomU, it w= ill break 00:02.0. Please note that this will work with 2.6.18.8 BR, Carsten. ----- Originalnachricht ----- Von: Carsten Schiers Gesendet: Son, 11.4.2010 16:45 An: xen-devel Cc: jeremy ; konrad.wilk Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.= 6.32 pvops kernels Two additional infos: here lspci of the two USB controllers. The 00:02.0 i= s passed into another DomU. I=20 should mention that I think the 00:02.0 is going down in case I pass 00:0= 2.1 into the 2.6.32 domain, but not if I pass it into the 2.6.31 domain. Find what the other DomU says be= low. 00:02.0 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3) (= prog-if 10 [OHCI]) Subsystem: Giga-byte Technology Device 5004 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParEr= r- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort- <= TAbort- SERR- TAbort- <= TAbort- SERR- 0002) [ 59.487005] ehci_hcd 0000:00:00.1: Xen PCI enabling IRQ: 20 [ 59.487005] xen_allocate_pirq: returning irq 20 for gsi 20 [ 59.487005] ehci_hcd 0000:00:00.1: EHCI Host Controller [ 59.491270] ehci_hcd 0000:00:00.1: new USB bus registered, assigned=20 bus number 1 [ 59.491409] ehci_hcd 0000:00:00.1: Enabling legacy PCI PM [ 59.491462] ehci_hcd 0000:00:00.1: debug port 1 [ 59.491534] ehci_hcd 0000:00:00.1: irq 20, io mem 0xc0201000 [ 59.497088] ehci_hcd 0000:00:00.1: USB 2.0 started, EHCI 1.00 [ 59.497182] usb usb1: New USB device found, idVendor=3D1d6b,=20 idProduct=3D0002 [ 59.497194] usb usb1: New USB device strings: Mfr=3D3, Product=3D2,=20 SerialNumber=3D1 [ 59.497207] usb usb1: Product: EHCI Host Controller [ 59.497216] usb usb1: Manufacturer: Linux 2.6.31.13-pvops-686=20 ehci_hcd [ 59.497228] usb usb1: SerialNumber: 0000:00:00.1 [ 59.497363] usb usb1: configuration #1 chosen from 1 choice [ 59.497447] hub 1-0:1.0: USB hub found [ 59.497643] hub 1-0:1.0: 10 ports detected Relevant XEN config entries in 2.6.32.11: CONFIG_XEN=3Dy CONFIG_XEN_MAX_DOMAIN_MEMORY=3D8 CONFIG_XEN_SAVE_RESTORE=3Dy # CONFIG_XEN_DEBUG_FS is not set CONFIG_SWIOTLB_XEN=3Dy CONFIG_MICROCODE_XEN=3Dy CONFIG_XEN_DOM0=3Dy CONFIG_XEN_PRIVILEGED_GUEST=3Dy CONFIG_XEN_DOM0_PCI=3Dy CONFIG_XEN_PCI_PASSTHROUGH=3Dy CONFIG_PCI_XEN=3Dy CONFIG_XEN_PCIDEV_FRONTEND=3Dy CONFIG_XEN_BLKDEV_FRONTEND=3Dy CONFIG_NETXEN_NIC=3Dm CONFIG_XEN_NETDEV_FRONTEND=3Dy CONFIG_XEN_KBDDEV_FRONTEND=3Dy CONFIG_HVC_XEN=3Dy CONFIG_XEN_FBDEV_FRONTEND=3Dy CONFIG_XEN_BALLOON=3Dy CONFIG_XEN_SCRUB_PAGES=3Dy CONFIG_XEN_DEV_EVTCHN=3Dy CONFIG_XEN_BACKEND=3Dy CONFIG_XEN_NETDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_BACKEND=3Dy CONFIG_XEN_BLKDEV_TAP=3Dy CONFIG_XEN_BLKBACK_PAGEMAP=3Dy CONFIG_XEN_PCIDEV_BACKEND=3Dy CONFIG_XEN_PCIDEV_BACKEND_VPCI=3Dy # CONFIG_XEN_PCIDEV_BACKEND_PASS is not set # CONFIG_XEN_PCIDEV_BACKEND_SLOT is not set # CONFIG_XEN_PCIDEV_BACKEND_CONTROLLER is not set # CONFIG_XEN_PCIDEV_BE_DEBUG is not set CONFIG_XENFS=3Dy CONFIG_XEN_COMPAT_XENFS=3Dy CONFIG_XEN_SYS_HYPERVISOR=3Dy CONFIG_XEN_XENBUS_FRONTEND=3Dy # CONFIG_XEN_GNTDEV is not set CONFIG_XEN_S3=3Dy BR, Carsten. -----Urspr=FCngliche Nachricht----- Von: Carsten Schiers=20 Gesendet: Samstag, 10. April 2010 11:27 An: 'Pasi K=E4rkk=E4inen' Cc: 'xen-devel'; 'jeremy'; 'konrad.wilk' Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 /=20 2.6.32 pvops kernels Hi folks, some progress: >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, not=20 >> working on xen/stable-2.6.32 on Xen 3.4.1 >>=20 ------------------------------------------------------------------------ >> --------------------------------------- >>=20 >> It will allow passthrough of all mentioned devices except one of the=20 PCI=20 >> controllers. It will not be detected. Using=20 >> xm pci-attach will produce an error: >>=20 >> troi kernel: [ 23.862294] ehci_hcd 0000:00:01.1: device not=20 >> available because of BAR 0 [0xfc102000-0xfc1020ff] collisions >> troi kernel: [ 61.942809] ohci_hcd 0000:00:01.0: device not=20 >> available because of BAR 0 [0xfc104000-0xfc104fff] collisions >>=20 >> I first tried only with the 2nd function (or whatever it is called),=20 but=20 >> as you see, we have the same error with both put into=20 >> the DomU. >> > >Have you seen this wiki page?: >http://wiki.xensource.com/xenwiki/XenPCIpassthrough > >Try the "I get "non-page-aligned MMIO BAR" error when trying to start=20 the guest" thing.. maybe it helps?=20 Did so and move to Xen 3.4.3-rc4 and latest 2.6.18.8 Dom0 kernel. It=20 works now with pvops 2.6.32.10 DomU kernel!!!=20 Thanks Pasi!!! Eventually, you may put on the Wiki Page an example with more than one=20 PCI device, so that hectic persons like me see better that a) it's without parenthesis and b) a comma separated=20 list ;o). BR, Carsten. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel