WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 2/3] ioemu: add libpci fixup to handle recent cha

To: Alexia Benington <alexbenington@xxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 2/3] ioemu: add libpci fixup to handle recent change in PCIUtils
From: Yu Zhao <yu.zhao@xxxxxxxxx>
Date: Fri, 27 Feb 2009 14:58:34 +0800
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 26 Feb 2009 22:58:13 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7969168f0902262103t2cc56ba4j8f7ef7d97ea29f75@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <7969168f0902262103t2cc56ba4j8f7ef7d97ea29f75@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Feb 27, 2009 at 01:03:44PM +0800, Alexia Benington wrote:
> Hi Yu,
> 
> What were the changes in libutils that triggered this patch?
> 
> I've been trying to get a domu guest to correctly use a passed through
> VGA card, and noticed that some IO mappings are not as what the driver
> in the guest expects to see. For example, one of the I/O range starts
> from C000h. After the fixup, it was changed to C200h. I'm suspecting
> this causes the guest driver not to work correctly, although there may
> be other reasons. What do you think?

The old libpci doesn't provide BAR flags in `pci_dev->base_addr' when
using sysfs method. This is inconsistent with what it does when using
proc or direct I/O access method. The fix of libpci makes the BAR flags
combined into `base_addr', which impacts applications (like Xen Qemu)
using `base_addr' without masking the flags. That's why the fix triggered
the patch you mentioned.

Can you please grab some logs?

cat /sys/bus/pci/devices/xx:xx.x/resource
lspci -s xx:xx.x -vvv
Qemu log under /var/log/xen/qemu-dm-xxx

I'll try to figure out what happened to your I/O mapping.

Thanks,
Yu

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