search for: do_pci_add

Hi, unfortunatly your latest change "AMD,IOMMU: Clean up old entries in remapping tables when creating new one" (Changeset 26517 in xen-unstable and 25975 in xen-4.2-testing) is causing a CPU0 Panic at boot for me. When i tried to boot latest versions of xen unstable or xen-testing, my dom0 gives me the message: (XEN) ************************************* (XEN) Panic on CPU 0: (XEN)

...xl_pci.c Thu Dec 08 17:43:29 2011 +0000 +++ b/tools/libxl/libxl_pci.c Fri Dec 09 12:01:16 2011 +0000 @@ -819,7 +819,8 @@ int libxl__device_pci_add(libxl__gc *gc, stubdomid = libxl_get_stubdom_id(ctx, domid); if (stubdomid != 0) { libxl_device_pci pcidev_s = *pcidev; - rc = do_pci_add(gc, stubdomid, &pcidev_s, starting); + /* stubdomain is always running by now, even at create time */ + rc = do_pci_add(gc, stubdomid, &pcidev_s, 0); if ( rc ) goto out; }

...n I issue this xl pci-assignable-list I have pci=['00:1a.0'] on the DomU config file I have added this iommu=soft and swiotlb=force both together and separately to the kernel command line in the DomU (running Debian 8), but I get the same error each time. libxl: error: libxl_pci.c:999:do_pci_add: xc_assign_device failed: Operation not permitted libxl: error: libxl_create.c:1424:domcreate_attach_pci: libxl_device_pci_add failed: -3 Can anyone suggest a cure for this? Many thanks Francis -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists...

...by: Patrick Colp <Patrick.Colp@citrix.com> Signed-off-by: Olaf Hering <olaf@aepfle.de> --- ioemu-remote/xenstore.c | 3 +++ 1 file changed, 3 insertions(+) --- ioemu-remote/xenstore.c +++ ioemu-remote/xenstore.c @@ -927,6 +927,9 @@ static void xenstore_process_dm_command_ do_pci_add(par); free(par); #endif + } else if (!strncmp(command, "flush-cache", len)) { + fprintf(logfile, "dm-command: flush caches\n"); + qemu_invalidate_map_cache(); } else { fprintf(logfile, "dm-command: unknown command\"%*s\"\n&...

...: 0000000000100000->000000000017c510 TOTAL: 0000000000000000->00000000ff800000 ENTRY ADDRESS: 00000000001015a0 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000005fb 1GB PAGES: 0x0000000000000001 libxl: error: libxl_pci.c:712:do_pci_add xc_assign_device failed Daemon running with PID 11389 Leading up to this error, I have done the following to put the device into what is supposedly an assignable state: # stop lightdm # echo 0000:00:01.0 > /sys/bus/pci/drivers/radeon/unbind # modprobe xen-pciback # echo 0000:00:01.0 > /sys/...

...ble-list > > I have pci=['00:1a.0'] on the DomU config file > I have added this iommu=soft and swiotlb=force both together and separately > to the kernel command line > in the DomU (running Debian 8), but I get the same error each time. > > libxl: error: libxl_pci.c:999:do_pci_add: xc_assign_device failed: Operation > not permitted > libxl: error: libxl_create.c:1424:domcreate_attach_pci: libxl_device_pci_add > failed: -3 Can you please attach the following: 1. The complete domU config file 2. A complete log of the command and all the output 3. The full output of &...

...t > > I have pci=['00:1a.0'] on the DomU config file > I have added this iommu=soft and swiotlb=force both together and separately > to the kernel command line > in the DomU (running Debian 8), but I get the same error each time. > > libxl: error: libxl_pci.c:999:do_pci_add: xc_assign_device failed: Operation > not permitted > libxl: error: libxl_create.c:1424:domcreate_attach_pci: libxl_device_pci_add > failed: -3 Can you please attach the following: 1. The complete domU config file 2. A complete log of the command and all the output 3. The full outp...

...: 0000000000100000->00000000001795d0 TOTAL: 0000000000000000->000000003e000000 ENTRY ADDRESS: 0000000000100000 xc: info: PHYSICAL MEMORY ALLOCATION: 4KB PAGES: 0x0000000000000200 2MB PAGES: 0x00000000000001ef 1GB PAGES: 0x0000000000000000 libxl: error: libxl_pci.c:712:do_pci_add xc_assign_device failed Daemon running with PID 2050

...K_DRIVER, dom, bus, dev, func); if ( lstat(path, &st) ) { if ( errno == ENOENT ) XL_LOG(ctx, XL_LOG_ERROR, PCI_BDF " is not assigned to pciback driver", @@ -598,8 +603,9 @@ static int pci_ins_check(libxl_ctx *ctx, return 1; } -static int do_pci_add(libxl_ctx *ctx, uint32_t domid, libxl_device_pci *pcidev) +static int do_pci_add(libxl_gc *gc, uint32_t domid, libxl_device_pci *pcidev) { + libxl_ctx *ctx = libxl_gc_owner(gc); char *path; char *state, *vdevfn; int rc, hvm; @@ -609,21 +615,21 @@ static int do_pci_add(libxl_ctx *...

Add commands to automatically prep devices for pass-through The current method for passing through devices requires users to either modify cryptic Linux boot parameters and reboot, or do a lot of manual reads and writes into sysfs nodes. This set of patches introduces commands to make this easier. It expands on the concept of "assignable" (from the list_assignable_devices command).

...0xff) << 8) | + ((pcidev->enable) ? 1 : 0); +} + static int pcidev_init(libxl_device_pci *pcidev, unsigned int domain, unsigned int bus, unsigned int dev, unsigned int func, unsigned int vdevfn) @@ -699,7 +708,7 @@ static int do_pci_add(libxl__gc *gc, uin } out: if (!libxl_is_stubdom(ctx, domid, NULL)) { - rc = xc_assign_device(ctx->xch, domid, pcidev->value); + rc = xc_assign_device(ctx->xch, domid, pcidev_value(pcidev)); if (rc < 0 && (hvm || errno != ENOSYS)) {...