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

[Xen-devel] pciback_field_is_dup needs a fix

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] pciback_field_is_dup needs a fix
From: Jambunathan K <jambunathan@xxxxxxxxxx>
Date: Fri, 09 Mar 2007 01:09:19 +0530
Cc: sanjeev@xxxxxxxxxx
Delivery-date: Thu, 08 Mar 2007 11:39:37 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 1.5.0.10 (Windows/20070221)
Shouldn't pciback_field_is_dup(dev, field->offset) be scoped to include the base_offset as well?

Currently with xen-3.0.4 the issue is this:

Adding of PCI_PM_CTRL (at offset 4) to the 'config_fields list' gets skipped because it ends up being a duplicate of PCI_COMMAND (at offset 4 as well). As a result when a PCI device behind a PCI frontend does a power up using pci_enable_device() the following message gets flashed on the console.

pciback 0000:0b:00.3: Driver tried to write to a read-only configuration space field at offset 0x84, size 2. This may be harmless, but if you have problems with your device:
1) see permissive attribute in sysfs
2) report problems to the xen-devel mailing list along with details of your device obtained from lspci.

Thanks,
Jambunathan K.


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