"pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log

* "pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0". in qemu-dm-example.hvm.log
@ 2013-11-02 14:57 成会明
  2013-11-04 18:14 ` Konrad Rzeszutek Wilk
  0 siblings, 1 reply; 3+ messages in thread
From: 成会明 @ 2013-11-02 14:57 UTC (permalink / raw)
  To: xen-devel

[-- Attachment #1.1: Type: text/plain, Size: 1301 bytes --]

hi, 

I want to pass through "01:00.0",declared as pci=['01:00.0'] in cfg file. but found  error log
"pt_iomul_init: Error: pt_iomul_init can't open file /dev/xen/pci_iomul: No such file or directory: 0x1:0x0.0x0".  in qemu-dm-example.hvm.log
In fact, /dev/xen/pci_iomul does not exist. 

So where /dev/xen/pci_iomul implemented ?
I have searched xen and linux code, found nothing. where pci_iomul device's code implemented ?

I check tools/qemu-xen-traditional/hw/pass-through.c. and found pt_iomul_init is called if CONFIG_STUBDOM not defined.
so should CONFIG_STUBDOM be defined ?

Below is part of pass-through.c.

#ifndef CONFIG_STUBDOM

#define PCI_IOMUL_DEV_PATH      "/dev/xen/pci_iomul"
static void pt_iomul_init(struct pt_dev *assigned_device,
                          uint8_t r_bus, uint8_t r_dev, uint8_t r_func)
{
    int fd = PCI_IOMUL_INVALID_FD;
    struct pci_iomul_setup setup = {
        .segment = 0,
        .bus = r_bus,
        .dev = r_dev,
        .func = r_func,
    };

    fd = open(PCI_IOMUL_DEV_PATH, O_RDWR);
    if ( fd < 0 ) {
        PT_LOG("Error: %s can't open file %s: %s: 0x%x:0x%x.0x%x\n",
               __func__, PCI_IOMUL_DEV_PATH, strerror(errno),
               r_bus, r_dev, r_func);
        fd = PCI_IOMUL_INVALID_FD;

[-- Attachment #1.2: Type: text/html, Size: 2831 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

^ permalink raw reply	[flat|nested] 3+ messages in thread