From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonard Michelet Subject: Re: pt_pci_write_config: Warning: Guest attempt to set address to unused Base Address Register. [00:03.0][Offset:30h][Length:4] Date: Tue, 14 Apr 2009 07:17:24 -0700 (PDT) Message-ID: <23040258.post@talk.nabble.com> References: <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F19@heavy-vm03.heavy.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <14D9C9E2ED61ED41BC3B37ACDF4E8800029E434B9F19@heavy-vm03.heavy.org.uk> 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@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Hi,=20 I can't tell you why it's not working but I might help you to understand th= e error message. Your driver is trying to write something at the address 0x30 in the PCI port. This address correspond to the ROM's card address in the address space (http://pficheux.free.fr/articles/lmf/pci/registres_pci.gif). Does your card use ROM? Usually, BARs and ROM are set while VM is starting (with remapping) and Xen flag unset BARs as "unused". So when strange drivers write things in unused PCI registers this error message warn you, but I'm not sure it stop the writing order. I have a card which work great despite these messages, so I don't think thi= s is the problem. I hope this will help you. Can I ask you what card do you try to use? Good luck. L=C3=A9onard http://pficheux.free.fr/articles/lmf/pci/registres_pci.gif Tim Moore-13 wrote: >=20 > Hi Ian, >=20 > I noticed that you updated the qemu-dm passthrough debug messages recentl= y > and was wondering if you could help me with this issue? > (Please see xen-devel postings for further info) >=20 > To sum things up, I have a non-hvm DomU with PCI Passthrough working > successfully. The problem is that this is not working for any hvm DomU. I= s > this BAR warning related to my issue? I`m assume the vendor driver is > attempting to set BAR and not just accepting the values passed in. >=20 > What I find strange is that I am using the vendor driver under the non-hv= m > DomU also. Maybe pcifront is doing something that qemu-dm is not ? >=20 > Here is the qemu-dm log output ... (relevant parts) >=20 > register_real_device: Assigning real physical device 03:00.0 ... > pt_register_regions: IO region registered (size=3D0x01000000 > base_addr=3D0xb2000000) > pt_register_regions: IO region registered (size=3D0x10000000 > base_addr=3D0xe000000c) > pt_register_regions: IO region registered (size=3D0x02000000 > base_addr=3D0xb0000004) > pt_register_regions: IO region registered (size=3D0x00000080 > base_addr=3D0x00001001) > pt_msi_setup: msi mapped with pirq ff > register_real_device: Real physical device 03:00.0 registered successfuly= ! > IRQ type =3D MSI-INTx > Register xen platform. > Done register platform. > 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/900c41f9-a3f6-d78f-2270-93e116ee07e7/vncpasswd. > I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:03.0][Offset:30h][Length:4] > pt_iomem_map: e_phys=3De0000000 maddr=3De0000000 type=3D8 len=3D268435456= index=3D1 > first_map=3D1 > cirrus vga map change while on lfb mode > pt_iomem_map: e_phys=3Df2000000 maddr=3Db0000000 type=3D0 len=3D33554432 = index=3D3 > first_map=3D1 > pt_iomem_map: e_phys=3Df4000000 maddr=3Db2000000 type=3D0 len=3D16777216 = index=3D0 > first_map=3D1 > pt_pci_write_config: Warning: Guest attempt to set address to unused Base > Address Register. [00:03.0][Offset:30h][Length:4] > pt_ioport_map: e_phys=3Dc200 pio_base=3D1000 len=3D128 index=3D5 first_ma= p=3D1 > mapping vram to f0000000 - f0400000 > 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. > track_dirty_vram(f0000000, 26) failed (-1, 22) > track_dirty_vram(f0000000, 26) failed (-1, 22) > track_dirty_vram(f0000000, 26) failed (-1, 22) > track_dirty_vram(f0000000, 26) failed (-1, 22) >=20 > Many Thanks, > Tim >=20 > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel >=20 >=20 --=20 View this message in context: http://www.nabble.com/pt_pci_write_config%3A-= Warning%3A-Guest-attempt-to-set-address-to-unused-Base-Address-Register.--0= 0%3A03.0--Offset%3A30h--Length%3A4--tp23022929p23040258.html Sent from the Xen - Dev mailing list archive at Nabble.com.