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: Tue, 13 Apr 2010 08:32:44 +0200 Message-ID: <21168790.101271140364006.JavaMail.root@uhura> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: 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: =?iso-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: jeremy , xen-devel , "konrad.wilk" List-Id: xen-devel@lists.xenproject.org I thought so, too, but this doesn't work either. And: it does work in 2.6= =2E18, as I think it's not realy two devices. One is OHCI, the other EHCI. BR, Carsten. ----- Originalnachricht ----- Von: Pasi K=E4rkk=E4inen Gesendet: Mon, 12.4.2010 15:07 An: Carsten Schiers Cc: jeremy ; xen-devel ;= konrad.wilk Betreff: Re: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2.= 6.32 pvops kernels On Mon, Apr 12, 2010 at 03:01:33PM +0200, Carsten Schiers wrote: > Yet another note: the kernel messages that break 00:02.0 come up when I= use 2.6.31 kernel, > that means, if it is passing through the 00:02.1 into the pvops DomU, i= t will break 00:02.0. >=20 > Please note that this will work with 2.6.18.8 >=20 Maybe both of these devices need to be passed through at the same time to= the same guest,=20 since they're part of the same device?=20 -- Pasi > BR, > Carsten. >=20 > ----- 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= =2E6.32 pvops kernels >=20 > Two additional infos: here lspci of the two USB controllers. The 00:02.= 0 is passed into another DomU. I=20 > should mention that I think the 00:02.0 is going down in case I pass 00= :02.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 b= elow. >=20 > 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- Par= Err- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort= - SERR- Latency: 0 (750ns min, 250ns max) > Interrupt: pin A routed to IRQ 21 > Region 0: Memory at c0200000 (32-bit, non-prefetchable) [size=3D= 4K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA PME(D0+,D1= +,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME- > Kernel driver in use: pciback > Kernel modules: ohci-hcd >=20 > 00:02.1 USB Controller: nVidia Corporation MCP65 USB Controller (rev a3= ) (prog-if 20 [EHCI]) > Subsystem: Giga-byte Technology Device 5004 > Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- Par= Err- Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=3Dfast >TAbort= - SERR- Interrupt: pin B routed to IRQ 20 > Region 0: Memory at c0201000 (32-bit, non-prefetchable) [disabl= ed] [size=3D256] > Capabilities: [44] Debug port: BAR=3D1 offset=3D0098 > Capabilities: [80] Power Management version 2 > Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=3D0mA PME(D0+,D1= +,D2+,D3hot+,D3cold+) > Status: D0 PME-Enable- DSel=3D0 DScale=3D0 PME+ > Kernel driver in use: pciback > Kernel modules: ehci-hcd >=20 > Apr 11 16:27:26 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:27:26 uhura kernel: usb 1-2: USB disconnect, address 3 > Apr 11 16:27:26 uhura kernel: kcapi: card 1 down. > Apr 11 16:27:26 uhura kernel: kcapi: Controller 1: fcusb-0003 unregiste= red > Apr 11 16:27:26 uhura kernel: fcusb: Driver 'fcusb' detached > Apr 11 16:27:26 uhura kernel: usb 1-2: new full speed USB device using o= hci_hcd and address 4 > Apr 11 16:27:27 uhura kernel: usb 1-2: configuration #1 chosen from 1 c= hoice > Apr 11 16:27:27 uhura kernel: fcusb: Driver 'fcusb' attached to stack. (= 152) > Apr 11 16:27:27 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:27:27 uhura kernel: kcapi: Controller 1: fcusb-0004 attached > Apr 11 16:27:27 uhura kernel: kcapi: card 1 "fcusb-0004" ready. > Apr 11 16:28:24 uhura kernel: fcusb: Rx URB status: -110 > Apr 11 16:28:24 uhura kernel: usb 1-2: USB disconnect, address 4 > Apr 11 16:28:25 uhura kernel: kcapi: card 1 down. > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0004 unregiste= red > Apr 11 16:28:25 uhura kernel: fcusb: Driver 'fcusb' detached > Apr 11 16:28:25 uhura kernel: usb 1-2: new full speed USB device using o= hci_hcd and address 5 > Apr 11 16:28:25 uhura kernel: usb 1-2: configuration #1 chosen from 1 c= hoice > Apr 11 16:28:25 uhura kernel: fcusb: Driver 'fcusb' attached to stack. (= 152) > Apr 11 16:28:25 uhura kernel: fcusb: Stack version 3.11-04 > Apr 11 16:28:25 uhura kernel: kcapi: Controller 1: fcusb-0005 attached > Apr 11 16:28:25 uhura kernel: kcapi: card 1 "fcusb-0005" ready. >=20 > BR, > Carsten. >=20 >=20 > -----Urspr=FCngliche Nachricht----- > Von: Carsten Schiers=20 > Gesendet: Sonntag, 11. April 2010 16:33 > An: xen-devel > Cc: jeremy; konrad.wilk > Betreff: AW: Re: [Xen-devel] Some test results on Xen 4.0 and 2.6.31 / 2= =2E6.32 pvops kernels >=20 > Hi, >=20 > I am sorry to say that I mixed something. What does work now is=20 > 2.6.31.13 kernel. The error > messages are gone now for 2.6.32.11, but it is still not functioning.=20 >=20 > So, with the 2.6.32.11 kernel, it will not recognize the same USB=20 > controller that is recognized=20 > by 2.6.31.13.=20 >=20 > When booting: >=20 > [ 0.168388] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 0.325746] alloc irq_desc for 503 on node 0 > [ 0.325753] alloc kstat_irqs on node 0 >=20 > When I detach and attach from Dom0, it will log in the DomU: >=20 > [ 202.660279] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 202.848550] pcifront pci-0: backend going away! > [ 202.857153] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 202.903310] pcifront pci-0: 22 freeing event channel 9 > [ 224.234600] pcifront pci-0: Installing PCI frontend > [ 224.237069] pcifront pci-0: Creating PCI Frontend Bus 0000:00 >=20 > In Dom0 we have: >=20 > ACPI: PCI interrupt for device 0000:00:02.1 disabled > pciback: vpci: 0000:00:02.1: assign to virtual slot 0 >=20 > For reference, the log entries when I detach/attach the device in=20 > 2.6.31.13: >=20 > [ 47.250686] usb usb1: USB disconnect, address 1 > [ 47.251155] ehci_hcd 0000:00:00.1: USB bus 1 deregistered > [ 47.349616] pcifront pci-0: Rescanning PCI Frontend Bus 0000:00 > [ 47.938006] pcifront pci-0: backend going away! > [ 47.941640] pcifront pci-0: Disconnecting PCI Frontend Buses > [ 47.946981] pcifront pci-0: Device is in 6 state. Need to change=20 > state on the privileged domain. > [ 47.952364] pcifront pci-0: Device is in 0 state. Need to change=20 > state on the privileged domain. > [ 47.957636] pcifront pci-0: 22 freeing event channel 9 > [ 58.832396] pcifront pci-0: Device is in 2 state. Need to change=20 > state on the privileged domain. > [ 58.840387] pcifront pci-0: Device is in 3 state. Need to change=20 > state on the privileged domain. > [ 58.868584] pcifront pci-0: Installing PCI frontend > [ 58.869661] pcifront pci-0: Creating PCI Frontend Bus 0000:00 > [ 59.487005] ehci_hcd 0000:00:00.1: enabling device (0000 -> 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 >=20 > Relevant XEN config entries in 2.6.32.11: >=20 > 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 >=20 > BR, > Carsten. >=20 > -----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 >=20 > Hi folks, some progress: >=20 > >> PCI controller / 2nd Function? / working in xen/master-2.6.32.13, no= t=20 >=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 >=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 >=20 > Thanks Pasi!!! >=20 > 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). >=20 > BR, > Carsten. >=20 >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20 >=20 >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel