|
»
Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
|
|
|
Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Mr. Teo En Ming (Zhang Enming)-2
::
Rate this Message:
Hi,
Anybody knows how to solve this problem? -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com My Secondary Blog: http://enmingteo.wordpress.com My Youtube videos: http://www.youtube.com/user/enmingteo Email: space.time.universe@... MSN: teoenming@... Mobile Phone (SingTel): +65-9648-9798 Mobile Phone (Starhub Prepaid): +65-8369-2618 Age: 31 (as at 30 Oct 2009) Height: 1.78 meters Race: Chinese Dialect: Hokkien Street: Bedok Reservoir Road Country: Singapore On Sun, Nov 1, 2009 at 10:07 PM, Mr. Teo En Ming (Zhang Enming) <space.time.universe@...> wrote: Hi All, _______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
|
|
Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Konrad Rzeszutek Wilk
::
Rate this Message:
On Sun, Nov 01, 2009 at 10:07:41PM +0800, Mr. Teo En Ming (Zhang Enming) wrote:
> Hi All, > > I have just installed Slackware64 13.0 64-bit Linux as HVM domU. Please > refer to > http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/for > more details and screenshots. > > I have tried to passthrough the firewire controller on Intel DQ45CB > motherboard to Slackware64 13.0 HVM domU but I can't load the kernel modules > for it. It looks as if they are were already loaded during bootup. If you want to re-load them, first do 'rmmod' for all of the modules associated with the card. But looking at your 'dmesg' output it looks as if it was loaded correctly? > > Please have a look at the following output within Slackware64 13.0 HVM domU. > > 00:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70) (prog-if 10 > [OHCI]) > Subsystem: Intel Corporation Device 1003 > Flags: bus master, medium devsel, latency 128, IRQ 36 Wow. IRQ 36? Hmm, well mmaybe that is OK since you are running under QEMU as HVM guest. Can you provide the lspci -vv output of the Dom0 and DomU, please? > Memory at e3001000 (32-bit, non-prefetchable) [size=4K] > Memory at e3002000 (32-bit, non-prefetchable) [size=4K] > Capabilities: [44] Power Management version 2 > Kernel driver in use: ohci1394 > Kernel modules: ohci1394 ... snup .. > dm-command: hot insert pass-through pci dev > register_real_device: Assigning real physical device 02:01.0 ... > pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No > such file or directory: 0x2:0x1.0x0 > pt_register_regions: IO region registered (size=0x00001000 > base_addr=0xd3801000) > pt_register_regions: IO region registered (size=0x00000100 > base_addr=0xd3800000) > register_real_device: Error: Binding of interrupt failed! rc=-1 > register_real_device: Real physical device 02:01.0 registered successfuly! > IRQ type = INTx Hmmm.. I think that message is misleading. The code shows that it failed to bind the PCI card (02:01:0) to an interrupt and disabled the card. Then it prints the 'registered succesfully!' which is incorrect. Can you provide the output of: - lspci -vvv (from Dom0) - lspci -vvv (from DomU) - cat /proc/interrupts (from Dom0) _before_ you launch any guests or call bind any devices to the pcistub/pciback. - cat /proc/interrupts (from DomU) after you launch it and try to do stuff with the firewire. For example try to pull videos from your camera via the firewire port. > cirrus vga map change while on lfb mode > pt_iomem_map: e_phys=e3001000 maddr=d3801000 type=0 len=4096 index=0 > first_map=1 > pt_iomem_map: e_phys=e3002000 maddr=d3800000 type=0 len=4096 index=1 > first_map=1 > mapping vram to e0000000 - e0400000 > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw > state. > platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro > state. > *pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:05.0][Offset:30h][Length:4]* It does pass it throught. I believe it is OK during the probing of the device - but it does not say what the value it tried to write, so it is unclear what it is doing at that point. > > The line immediately above looks very suspicious. > > -- > Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical > Engineering) > Alma Maters: > (1) Singapore Polytechnic > (2) National University of Singapore > My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com > My Secondary Blog: http://enmingteo.wordpress.com > My Youtube videos: http://www.youtube.com/user/enmingteo > Email: space.time.universe@... > MSN: teoenming@... > Mobile Phone (SingTel): +65-9648-9798 > Mobile Phone (Starhub Prepaid): +65-8369-2618 > Age: 31 (as at 30 Oct 2009) > Height: 1.78 meters > Race: Chinese > Dialect: Hokkien > Street: Bedok Reservoir Road > Country: Singapore > > On Sat, Oct 24, 2009 at 2:19 AM, Mr. Teo En Ming (Zhang Enming) < > space.time.universe@...> wrote: > > > From the screenshots of the device manager in the Win XP Home domU, > > the OHCI IEEE 1394 firewire controller appears to be working properly. > > The Windows drivers for the firewire controller reports that the > > firewire controller is working fine. > > > > However, when you connect a firewire-based digital video camera to the > > firewire port, it is not detected in the Windows virtual machine. > > > > I will probably have to find time to install a Linux HVM domU and try > > to pass through the 1394 controller to it. > > > > -- > > Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical > > Engineering) > > Alma Maters: > > (1) Singapore Polytechnic > > (2) National University of Singapore > > Blog URL: http://teo-en-ming-aka-zhang-enming.blogspot.com > > Email: space.time.universe@... > > MSN: teoenming@... > > Mobile Phone: +65-9648-9798 > > Street: Bedok Reservoir Road > > Republic of Singapore > > > > > > On Sat, Oct 24, 2009 at 1:57 AM, Konrad Rzeszutek Wilk > > <konrad.wilk@...> wrote: > > > On Sat, Oct 24, 2009 at 01:47:31AM +0800, Mr. Teo En Ming (Zhang Enming) > > wrote: > > >> Hi, > > >> > > >> Could you help me look at here > > >> > > http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01149.html > > >> and also here > > http://lists.xensource.com/archives/html/xen-devel/2009-10/msg01134.html > > > > > > Its looks to be working from the Dom0 side just fine. I am curious as > > what is happening > > > on the Windows driver side. I don't know enough about where Windows > > drivers put > > > debug information so I can't suggest where to look there. One suggestion > > is that > > > you install Fedora Core 11 as a HVM guest and passthrough your firewire > > controller to it. > > > And then include the logs from the Fedora domU - that should give more > > insight on why > > > it is not working properly. > > > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@... > http://lists.xensource.com/xen-devel _______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
|
|
RE: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Han, Weidong
::
Rate this Message:
Hi En Ming,
I found the line "register_real_device: Error: Binding of interrupt failed!
rc=-1". So I guess the Fire-wire device doesn't
support MSI, and shares IRQ with other devices. This is the issue I and Jeremy
are discussing. You can search mail subject "pv-ops: fix shared irq device
passthrough" in mailing list for more details. Pls apply the attached patch
to pv-ops dom0 see if it fixes your problem.
Regards,
Weidong From: Mr. Teo En Ming (Zhang Enming) [mailto:space.time.universe@...] Sent: 2009年11月1日 22:08 To: Konrad Rzeszutek Wilk Cc: Jeremy Fitzhardinge; xen-devel@...; Han, Weidong; space.time.universe@...; xen-users@... Subject: Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1) I have just installed Slackware64 13.0 64-bit Linux as HVM domU. Please refer to http://enmingteo.wordpress.com/2009/11/01/picture-tutorial-how-to-setup-slackware64-13-0-hvm-domu-with-xen-3-5-unstable-pv-ops-dom0-kernel-2-6-31-4-in-fedora-11-x86-64-dom0/ for more details and screenshots. I have tried to passthrough the firewire controller on Intel DQ45CB motherboard to Slackware64 13.0 HVM domU but I can't load the kernel modules for it. Please have a look at the following output within Slackware64 13.0 HVM domU. 00:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70) (prog-if 10 [OHCI]) Subsystem: Intel Corporation Device 1003 Flags: bus master, medium devsel, latency 128, IRQ 36 Memory at e3001000 (32-bit, non-prefetchable) [size=4K] Memory at e3002000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Kernel driver in use: ohci1394 Kernel modules: ohci1394 root@slackware64-13:~# lsmod | egrep "(ohci|1394)" root@slackware64-13:~# cd /lib/modules/2.6.29.6/kernel/drivers/ieee1394/ root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# ls dv1394.ko eth1394.ko ieee1394.ko ohci1394.ko pcilynx.ko raw1394.ko sbp2.ko video1394.ko root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# modinfo ohci1394.ko filename: ohci1394.ko license: GPL description: Driver for PCI OHCI IEEE-1394 controllers author: Sebastien Rougeaux <sebastien.rougeaux@...> alias: pci:v*d*sv*sd*bc0Csc00i10* depends: ieee1394 vermagic: 2.6.29.6 SMP mod_unload parm: phys_dma:Enable physical DMA (default = 1). (int) root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# modinfo ieee1394.ko filename: ieee1394.ko license: GPL depends: vermagic: 2.6.29.6 SMP mod_unload parm: ignore_drivers:Disable automatic probing for drivers. (int) parm: fcp:Map FCP registers (default = 1, disable = 0). (int) parm: disable_nodemgr:Disable nodemgr functionality. (int) parm: disable_irm:Disable Isochronous Resource Manager functionality. (bool) root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# modprobe ieee1394 FATAL: Error inserting ieee1394 (/lib/modules/2.6.29.6/kernel/drivers/ieee1394/ieee1394.ko): Invalid argument root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# modprobe ohci1394 FATAL: Error inserting ohci1394 (/lib/modules/2.6.29.6/kernel/drivers/ieee1394/ohci1394.ko): Invalid argument root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# dmesg | grep -i firewire root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# dmesg | grep -i ieee ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# lsmod | grep ieee1394 root@slackware64-13:/lib/modules/2.6.29.6/kernel/drivers/ieee1394# dmesg | grep 1394 ohci1394 0000:00:05.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 ohci1394: fw-host0: OHCI-1394 1.0 (PCI): IRQ=[36] MMIO=[e3001000-e30017ff] Max Packet=[2048] IR/IT contexts=[8/8] ieee1394: module is already loaded ohci1394: module is already loaded ieee1394: module is already loaded ohci1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ieee1394: module is already loaded ohci1394: module is already loaded Debug messages in Dom0: domid: 3 qemu: the number of cpus is 2 config qemu network with xen bridge for tap3.0 eth0 Watching /local/domain/0/device-model/3/logdirty/next-active Watching /local/domain/0/device-model/3/command qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 9a35fdea-fa74-6fec-e0f2-a852836d9a22 Time offset set 0 cirrus_vga_enabled populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. xs_read(/vm/9a35fdea-fa74-6fec-e0f2-a852836d9a22/log-throttling): read error platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/3/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/9a35fdea-fa74-6fec-e0f2-a852836d9a22/vncpasswd. medium change watch on `hdc' (index: 1): /media/hitachi/slackware64-13.0-install-dvd.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 02:01.0 ... pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x1.0x0 pt_register_regions: IO region registered (size=0x00001000 base_addr=0xd3801000) pt_register_regions: IO region registered (size=0x00000100 base_addr=0xd3800000) register_real_device: Error: Binding of interrupt failed! rc=-1 register_real_device: Real physical device 02:01.0 registered successfuly! IRQ type = INTx cirrus vga map change while on lfb mode pt_iomem_map: e_phys=e3001000 maddr=d3801000 type=0 len=4096 index=0 first_map=1 pt_iomem_map: e_phys=e3002000 maddr=d3800000 type=0 len=4096 index=1 first_map=1 mapping vram to e0000000 - e0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:30h][Length:4] The line immediately above looks very suspicious. -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com My Secondary Blog: http://enmingteo.wordpress.com My Youtube videos: http://www.youtube.com/user/enmingteo Email: space.time.universe@... MSN: teoenming@... Mobile Phone (SingTel): +65-9648-9798 Mobile Phone (Starhub Prepaid): +65-8369-2618 Age: 31 (as at 30 Oct 2009) Height: 1.78 meters Race: Chinese Dialect: Hokkien Street: Bedok Reservoir Road Country: Singapore On Sat, Oct 24, 2009 at 2:19 AM, Mr. Teo En Ming (Zhang
Enming) <space.time.universe@...>
wrote: From the screenshots of the device manager in the Win XP Home domU, _______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
|
|
Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Mr. Teo En Ming (Zhang Enming)-2
::
Rate this Message:
Hi Weidong,
I have applied the patch to pv-ops dom0 kernel 2.6.31.5. Please refer to the following link: http://enmingteo.files.wordpress.com/2009/11/screenshot-01.png It does however cause my console terminal in dom0 to be very sluggish/unresponsive after I have started Slackware64 13.0 HVM. Here is my qemu-dm-slackware64.log output: domid: 1 qemu: the number of cpus is 2 config qemu network with xen bridge for tap1.0 eth0 Watching /local/domain/0/device-model/1/logdirty/next-active Watching /local/domain/0/device-model/1/command qemu_map_cache_init nr_buckets = 10000 size 4194304 shared page at pfn feffd buffered io page at pfn feffb Guest uuid = 4d2942cf-1ba2-0ff1-4252-184d1ab31369 Time offset set 0 cirrus_vga_enabled populating video RAM at ff000000 mapping video RAM from ff000000 Register xen platform. Done register platform. xs_read(/vm/4d2942cf-1ba2-0ff1-4252-184d1ab31369/log-throttling): read error platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. xs_read(/local/domain/0/device-model/1/xen_extended_power_mgmt): read error xs_read(): vncpasswd get error. /vm/4d2942cf-1ba2-0ff1-4252-184d1ab31369/vncpasswd. medium change watch on `hdc' (index: 1): /media/hitachi/slackware64-13.0-install-dvd.iso I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 dm-command: hot insert pass-through pci dev register_real_device: Assigning real physical device 02:01.0 ... pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x2:0x1.0x0 pt_register_regions: IO region registered (size=0x00001000 base_addr=0xd3801000) pt_register_regions: IO region registered (size=0x00000100 base_addr=0xd3800000) register_real_device: Real physical device 02:01.0 registered successfuly! IRQ type = INTx cirrus vga map change while on lfb mode pt_iomem_map: e_phys=e3001000 maddr=d3801000 type=0 len=4096 index=0 first_map=1 pt_iomem_map: e_phys=e3002000 maddr=d3800000 type=0 len=4096 index=1 first_map=1 mapping vram to e0000000 - e0400000 platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw state. platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro state. pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:30h][Length:4] Here is my domU lspci -vvv output: 00:05.0 FireWire (IEEE 1394): Agere Systems FW322/323 (rev 70) (prog-if 10 [OHCI]) Subsystem: Intel Corporation Device 1003 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 128 (3000ns min, 6000ns max) Interrupt: pin A routed to IRQ 36 Region 0: Memory at e3001000 (32-bit, non-prefetchable) [size=4K] Region 1: Memory at e3002000 (32-bit, non-prefetchable) [size=4K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ohci1394 Kernel modules: ohci1394 Here is my domU /proc/interrupts output: CPU0 CPU1 0: 132 0 IO-APIC-edge timer 1: 176 181 IO-APIC-edge i8042 4: 0 1 IO-APIC-edge 6: 1 2 IO-APIC-edge floppy 7: 0 0 IO-APIC-edge parport0 8: 1 0 IO-APIC-edge rtc0 9: 0 0 IO-APIC-fasteoi acpi 12: 518 632 IO-APIC-edge i8042 14: 2600 2591 IO-APIC-edge ide0 15: 2023 2073 IO-APIC-edge ide1 32: 174 167 IO-APIC-fasteoi eth0 36: 842 815 IO-APIC-fasteoi ohci1394 NMI: 0 0 Non-maskable interrupts LOC: 1362927 1362831 Local timer interrupts RES: 2164 2467 Rescheduling interrupts CAL: 10 38 Function call interrupts TLB: 323 324 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts SPU: 0 0 Spurious interrupts ERR: 0 MIS: 0 I still cannot load the kernel modules for the firewire controller in domU. root@slackware64-13:~# modprobe ieee1394 FATAL: Error inserting ieee1394 (/lib/modules/2.6.29.6/kernel/drivers/ieee1394/ieee1394.ko): Invalid argument root@slackware64-13:~# modprobe ohci1394 FATAL: Error inserting ohci1394 (/lib/modules/2.6.29.6/kernel/drivers/ieee1394/ohci1394.ko): Invalid argument Here is my /proc/interrupts output in dom0 AFTER I have started Slackware64 domU: CPU0 CPU1 1: 2 0 xen-pirq-ioapic-edge i8042 4: 3 0 xen-pirq-ioapic-edge 8: 1 0 xen-pirq-ioapic-edge rtc0 9: 0 0 xen-pirq-ioapic-level acpi 12: 4 0 xen-pirq-ioapic-edge i8042 16: 0 0 xen-pirq-ioapic-level uhci_hcd:usb3 17: 1 0 xen-pirq-ioapic-level 18: 59 0 xen-pirq-ioapic-level ehci_hcd:usb1, uhci_hcd:usb5, uhci_hcd:usb8 19: 60581 0 xen-pirq-ioapic-level ata_piix, ata_piix, uhci_hcd:usb7 21: 0 0 xen-pirq-ioapic-level uhci_hcd:usb4 22: 2500 0 xen-pirq-ioapic-level HDA Intel 23: 35508 0 xen-pirq-ioapic-level ehci_hcd:usb2, uhci_hcd:usb6 24: 121214 0 xen-dyn-virq timer0 25: 290373 0 xen-dyn-ipi resched0 26: 0 0 xen-dyn-ipi callfunc0 27: 0 0 xen-dyn-virq debug0 28: 213 0 xen-dyn-ipi callfuncsingle0 29: 0 3091038 xen-dyn-virq timer1 30: 0 76203 xen-dyn-ipi resched1 31: 0 0 xen-dyn-ipi callfunc1 32: 0 0 xen-dyn-virq debug1 33: 0 644 xen-dyn-ipi callfuncsingle1 34: 87 1002 xen-dyn-event xenbus 36: 0 0 xen-dyn-virq mce 38: 8967 5621 xen-pirq-msi peth0 39: 61 563 xen-dyn-event evtchn:xenstored 40: 0 0 xen-dyn-event evtchn:xenstored 42: 1 0 xen-dyn-event evtchn:xenstored 43: 4098 462204 xen-dyn-event evtchn:qemu-dm 44: 8156 115233 xen-dyn-event evtchn:qemu-dm NMI: 0 0 Non-maskable interrupts LOC: 0 0 Local timer interrupts SPU: 0 0 Spurious interrupts CNT: 0 0 Performance counter interrupts PND: 0 0 Performance pending work RES: 290373 76203 Rescheduling interrupts CAL: 213 644 Function call interrupts TLB: 0 0 TLB shootdowns TRM: 0 0 Thermal event interrupts THR: 0 0 Threshold APIC interrupts MCE: 0 0 Machine check exceptions MCP: 6 6 Machine check polls ERR: 0 MIS: 0 -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com My Secondary Blog: http://enmingteo.wordpress.com My Youtube videos: http://www.youtube.com/user/enmingteo Email: space.time.universe@... Mobile Phone (Starhub Prepaid): +65-8369-2618 Street: Bedok Reservoir Road Country: Singapore 2009/11/3 Han, Weidong <weidong.han@...>
_______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
|
|
Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Mr. Teo En Ming (Zhang Enming)-2
::
Rate this Message:
After applying the patch to pv-ops dom0 kernel 2.6.31.5, the error "register_real_device: Error: Binding of interrupt failed! rc=-1" disappears but the following message still persists.
pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:30h][Length:4] Do we need to do something about the BARs just like in VGA pass-through? -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com My Secondary Blog: http://enmingteo.wordpress.com My Youtube videos: http://www.youtube.com/user/enmingteo Email: space.time.universe@... Mobile Phone (Starhub Prepaid): +65-8369-2618 Street: Bedok Reservoir Road Country: Singapore 2009/11/3 Mr. Teo En Ming (Zhang Enming) <space.time.universe@...> Hi Weidong, _______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
|
|
RE: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1)
by Han, Weidong
::
Rate this Message:
I didn't pass-through Fire-wire, and I'm not
familar with it. You only pass-through 02:01.0, why did it access
00:05.0?
Regards,
Weidong From: Mr. Teo En Ming (Zhang Enming) [mailto:space.time.universe@...] Sent: 2009年11月3日 21:06 To: Han, Weidong Cc: Konrad Rzeszutek Wilk; Jeremy Fitzhardinge; xen-devel@...; xen-users@...; space.time.universe@... Subject: Re: [Xen-devel] Re: Fire-wire passthrough with Linux pv-ops (2.6.31.1) pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:05.0][Offset:30h][Length:4] Do we need to do something about the BARs just like in VGA pass-through? -- Mr. Teo En Ming (Zhang Enming) Dip(Mechatronics) BEng(Hons)(Mechanical Engineering) Alma Maters: (1) Singapore Polytechnic (2) National University of Singapore My Primary Blog: http://teo-en-ming-aka-zhang-enming.blogspot.com My Secondary Blog: http://enmingteo.wordpress.com My Youtube videos: http://www.youtube.com/user/enmingteo Email: space.time.universe@... Mobile Phone (Starhub Prepaid): +65-8369-2618 Street: Bedok Reservoir Road Country: Singapore 2009/11/3 Mr. Teo En Ming (Zhang Enming) <space.time.universe@...> Hi Weidong, _______________________________________________ Xen-users mailing list Xen-users@... http://lists.xensource.com/xen-users |
0001-pv-ops-fix-shared-irq-device-passthrough-v2.patch (5K) | Free embeddable forum powered by Nabble | Forum Help |
