search for: resource_align

Isn''t the correct syntax supposed to be pci=resource_alignment=03:04.0;06:00.0;0a:06.1? I get error: unknown command `06:00.0''. error: unknown command `0a:06.1''. when booting. Thank you, Darkbasic _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users

Hello all, I''m trying to pass my PCI device through to an HVM. I''m following the steps on the xen pci passthrough wiki. First I check my pci devices #lspci - 03:00.0 VGA compatible controller: ATI Technologies Inc Device 671d 03:00.1 Audio device: ATI Technologies Inc Device aa80 04:00.0 Display controller: ATI Technologies Inc Device 671d 04:00.1 Audio device: ATI

...----- After a while I found out that this errors also could be find in the working 2.6.27-kernel. So I guess that could not be what caused this mess. :) While I write this mail I found the solution… *DANCING* So for all who are struggling with this akward error: -> xen-pciback.hide=(X:XX.X) pci=resource_alignment=XX:XX.X <- works for me! ---- title Xen 3.4.2 / 2.6.31.12-xen4 root (hd0,6) kernel /boot/xen-3.4.2.gz module /boot/vmlinuz-2.6.31.12-xen4 root=/dev/sda7 ro console=tty0 pci=nomsi noreboot xen-pciback.hide=(01:07.0) pci=resource_alignment=01:07.0 module...

testing, uname -ri 2.6.33-rc5-4-xen x86_64 rpm -qa | grep -i Xen-4 xen-4.0.0_20873_01-29.1.x86_64 cat test.cfg name = ''test'' builder = ''linux'' bootloader = ''/usr/lib/xen/boot/domUloader.py'' bootargs = ''--entry=xvda1:vmlinuz-xen,/boot/initrd-xen'' disk = [

...>resource[i], i); + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) + pci_update_resource(dev, i); } static struct pci_platform_pm_ops *pci_platform_pm; @@ -1864,6 +1849,53 @@ int pci_select_bars(struct pci_dev *dev, unsigned long flags) return bars; } +/** + * pci_resource_alignment - get a PCI BAR resource alignment + * @dev: the PCI device + * @resno: the resource number + * + * Returns alignment size on success, or 0 on error. + */ +int pci_resource_alignment(struct pci_dev *dev, int resno) +{ + resource_size_t align; + struct resource *res = dev->resourc...

...>resource[i], i); + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) + pci_update_resource(dev, i); } static struct pci_platform_pm_ops *pci_platform_pm; @@ -1864,6 +1849,53 @@ int pci_select_bars(struct pci_dev *dev, unsigned long flags) return bars; } +/** + * pci_resource_alignment - get a PCI BAR resource alignment + * @dev: the PCI device + * @resno: the resource number + * + * Returns alignment size on success, or 0 on error. + */ +int pci_resource_alignment(struct pci_dev *dev, int resno) +{ + resource_size_t align; + struct resource *res = dev->resourc...

...f (r->parent || (r->flags & mask) != type) continue; - r_size = r->end - r->start + 1; + r_size = resource_size(r); /* For bridges size != alignment */ align = resource_alignment(r); order = __ffs(align) - 20; diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c index 1a5fc83..56e4042 100644 --- a/drivers/pci/setup-res.c +++ b/drivers/pci/setup-res.c @@ -133,7 +133,7 @@ int pci_assign_resource(struct pci_dev *dev, int resno) res...

...f (r->parent || (r->flags & mask) != type) continue; - r_size = r->end - r->start + 1; + r_size = resource_size(r); /* For bridges size != alignment */ align = resource_alignment(r); order = __ffs(align) - 20; diff --git a/drivers/pci/setup-res.c b/drivers/pci/setup-res.c index 1a5fc83..56e4042 100644 --- a/drivers/pci/setup-res.c +++ b/drivers/pci/setup-res.c @@ -133,7 +133,7 @@ int pci_assign_resource(struct pci_dev *dev, int resno) res...

...resource(dev, &dev->resource[i], i); + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) + pci_update_resource(dev, i); } static struct pci_platform_pm_ops *pci_platform_pm; @@ -1864,6 +1849,53 @@ int pci_select_bars(struct pci_dev *dev, unsigned long flags) return bars; } +/** + * pci_resource_alignment - get a PCI BAR resource alignment + * @dev: the PCI device + * @resno: the resource number + * + * Returns alignment size on success, or 0 on error. + */ +int pci_resource_alignment(struct pci_dev *dev, int resno) +{ + resource_size_t align; + struct resource *res = dev->resource + resno; +...

...resource(dev, &dev->resource[i], i); + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) + pci_update_resource(dev, i); } static struct pci_platform_pm_ops *pci_platform_pm; @@ -1864,6 +1849,53 @@ int pci_select_bars(struct pci_dev *dev, unsigned long flags) return bars; } +/** + * pci_resource_alignment - get a PCI BAR resource alignment + * @dev: the PCI device + * @resno: the resource number + * + * Returns alignment size on success, or 0 on error. + */ +int pci_resource_alignment(struct pci_dev *dev, int resno) +{ + resource_size_t align; + struct resource *res = dev->resource + resno; +...

...resource(dev, &dev->resource[i], i); + for (i = 0; i < PCI_BRIDGE_RESOURCES; i++) + pci_update_resource(dev, i); } static struct pci_platform_pm_ops *pci_platform_pm; @@ -1864,6 +1849,53 @@ int pci_select_bars(struct pci_dev *dev, unsigned long flags) return bars; } +/** + * pci_resource_alignment - get a PCI BAR resource alignment + * @dev: the PCI device + * @resno: the resource number + * + * Returns alignment size on success, or 0 on error. + */ +int pci_resource_alignment(struct pci_dev *dev, int resno) +{ + resource_size_t align; + struct resource *res = dev->resource + resno; +...

...ge this file, run ''update-grub'' afterwards to update # /boot/grub/grub.cfg. GRUB_DEFAULT=0 GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet xen-pciback.permissive xen-pciback.hide=(01:00.0)(03:00.0) pci=resource_alignment=01:00.0;03:00.0" GRUB_CMDLINE_LINUX="" root@omega:~# xm pci-list-assignable-devices 0000:03:00.0 0000:01:00.0 the LAN device works perfectly on the DomU configured with it but it fails on the WLAN one: root@omega:~# cat /etc/xen/AccessPoint.cfg # # Configuration file...

...nown device 10a7 (rev 02) 05:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) 05:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) my *intent* it to let domU to use "05:00.0" device. boot dom0 with "pci=resource_alignment=05:00.0 xen-pciback.hide=(05:00.0)" appended my domU config file is disk = [''tap:aio:/domU.image,xvda1,w'', ''tap:aio:/domUswap.image,xvda2,w''] kernel = "/bzImage" vcpus=2 vif = [ "mac=00:15:17:AC:00:40,ip=128.224.165.204" ] root = &...

...0000:05:00.0: seizing device [ 1.880482] pciback 0000:05:00.1: seizing device [ 1.880539] pciback 0000:05:00.2: seizing device root@vm:~# cat /boot/grub/grub.cfg | grep pciback module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro pci=resource_alignment=05:00.0 xen-pciback.permissive xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2) root@vm:~# xm info host : vm release : 2.6.32-5-xen-amd64 version : #1 SMP Sat Oct 30 17:04:10 UTC 2010 machine : x86_64 nr_cpus : 8 nr_node...

...0000:05:00.0: seizing device [ 1.880482] pciback 0000:05:00.1: seizing device [ 1.880539] pciback 0000:05:00.2: seizing device root@vm:~# cat /boot/grub/grub.cfg | grep pciback module /boot/vmlinuz-2.6.32-5-xen-amd64 placeholder root=UUID=aebc8747-abb3-413a-b808-b345a9a19111 ro pci=resource_alignment=05:00.0 xen-pciback.permissive xen-pciback.hide=(05:00.0)(05:00.1)(05:00.2) root@vm:~# xm info host : vm release : 2.6.32-5-xen-amd64 version : #1 SMP Sat Oct 30 17:04:10 UTC 2010 machine : x86_64 nr_cpus : 8 nr_node...

...software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. [PATCH 1/8 v4] PCI: define PCI resource names in a 'enum' [PATCH 2/8 v4] PCI: export __pci_read_base [PATCH 3/8 v4] PCI: export pci_alloc_child_bus [PATCH 4/8 v4] PCI: add a wrapper for resource_alignment [PATCH 5/8 v4] PCI: add a new function to map BAR offset [PATCH 6/8 v4] PCI: support the SR-IOV capability [PATCH 7/8 v4] PCI: reserve bus range for the SR-IOV device [PATCH 8/8 v4] PCI: document the changes --- b/Documentation/DocBook/kernel-api.tmpl | 1 b/Documentation/PCI/pci-iov-how...

...software perspective, which will benefit KVM and achieve other purposes such as QoS, security, and etc. [PATCH 1/8 v4] PCI: define PCI resource names in a 'enum' [PATCH 2/8 v4] PCI: export __pci_read_base [PATCH 3/8 v4] PCI: export pci_alloc_child_bus [PATCH 4/8 v4] PCI: add a wrapper for resource_alignment [PATCH 5/8 v4] PCI: add a new function to map BAR offset [PATCH 6/8 v4] PCI: support the SR-IOV capability [PATCH 7/8 v4] PCI: reserve bus range for the SR-IOV device [PATCH 8/8 v4] PCI: document the changes --- b/Documentation/DocBook/kernel-api.tmpl | 1 b/Documentation/PCI/pci-iov-how...

...[PATCH 1/15 v5] PCI: remove unnecessary arg of pci_update_resource() [PATCH 2/15 v5] PCI: define PCI resource names in an 'enum' [PATCH 3/15 v5] PCI: export __pci_read_base [PATCH 4/15 v5] PCI: make pci_alloc_child_bus() be able to handle bridge device [PATCH 5/15 v5] PCI: add a wrapper for resource_alignment() [PATCH 6/15 v5] PCI: add a new function to map BAR offset [PATCH 7/15 v5] PCI: cleanup pcibios_allocate_resources() [PATCH 8/15 v5] PCI: add boot option to reassign resources [PATCH 9/15 v5] PCI: add boot option to align MMIO resource [PATCH 10/15 v5] PCI: cleanup pci_bus_add_devices() [PATCH...

...[PATCH 1/15 v5] PCI: remove unnecessary arg of pci_update_resource() [PATCH 2/15 v5] PCI: define PCI resource names in an 'enum' [PATCH 3/15 v5] PCI: export __pci_read_base [PATCH 4/15 v5] PCI: make pci_alloc_child_bus() be able to handle bridge device [PATCH 5/15 v5] PCI: add a wrapper for resource_alignment() [PATCH 6/15 v5] PCI: add a new function to map BAR offset [PATCH 7/15 v5] PCI: cleanup pcibios_allocate_resources() [PATCH 8/15 v5] PCI: add boot option to reassign resources [PATCH 9/15 v5] PCI: add boot option to align MMIO resource [PATCH 10/15 v5] PCI: cleanup pci_bus_add_devices() [PATCH...

Hello, I am trying to pass my LSI SAS 2008 controller to my PV domu (openindiana) and I can not get it working. I have read that xen does not support the loading of option ROM''s in pv domu''s and that this support is being, or will be, added. http://markmail.org/thread/2njw43iaurmvzlys This post is more than a year old now. I am wondering if there is a way to get my LSI SAS