search for: device_cr

This is a small fix of the error handling in device_create(). Signed-off-by: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com> Regards, ----------------------- Yosuke Iwamatsu NEC Corporation _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

..., mdev->aper.len); > + if (!mdev->aper.va) { > + dev_err(&pdev->dev, "Cannot remap Aperture BAR\n"); > + rc = -EIO; > + goto unmap_mmio; > + } > + > + mdev->ops->init(mdev); > + > + pci_set_drvdata(pdev, mdev); > + > + mdev->sdev = device_create(g_mic.mic_class, &pdev->dev, > + MKDEV(MAJOR(g_mic.mdev_id), mdev->id), NULL, "%s", mdev->name); > + if (IS_ERR(mdev->sdev)) { > + rc = PTR_ERR(mdev->sdev); > + dev_err(&pdev->dev, "device_create failed rc %d\n", rc); > + goto unm...

..., mdev->aper.len); > + if (!mdev->aper.va) { > + dev_err(&pdev->dev, "Cannot remap Aperture BAR\n"); > + rc = -EIO; > + goto unmap_mmio; > + } > + > + mdev->ops->init(mdev); > + > + pci_set_drvdata(pdev, mdev); > + > + mdev->sdev = device_create(g_mic.mic_class, &pdev->dev, > + MKDEV(MAJOR(g_mic.mdev_id), mdev->id), NULL, "%s", mdev->name); > + if (IS_ERR(mdev->sdev)) { > + rc = PTR_ERR(mdev->sdev); > + dev_err(&pdev->dev, "device_create failed rc %d\n", rc); > + goto unm...

...h file based disk to the this domU. My command is: # xm block-attach Ubuntu-11 file:/root/ubunut-natty/Extra /dev/xvdb w there is no error on this. But inside the DomU i cannot see any disk xvdb. xend.log shows : [2011-10-25 16:27:32 14794] DEBUG (XendDomainInfo:853) XendDomainInfo.device_create: {''uuid'': ''18743cdb-d88a-84e3-c2e4-c5c726e06cda'', ''bootable'': 0, ''driver'': ''paravirtualised'', ''dev'': ''/dev/xvdb'', ''uname'': ''file:/root/ubunut-...

Still trying to make my VMs appear on a subnet of their very own and route traffic to/from them from the Dom0. This network-multinet script sounds ideal for what I want: http://thepenguinpriest.com/linux/scripts/network-multinet.html However, the description of building a routed network says I need to call the script and give it the "virtual ethernet device (vethX)" that lives in

Hi, I tried to attach passrough io device to domU, the command (ended successfully in dom0), but when I entered the domU and typed the "lspci" command I didn''t see the new device, although the dom0 removed it from the "pci-list-assignable-devices". When I tried to detach it from the domU, the detach command returned with timeout error. What did I miss? perhaps I

Hi all, I downloaded the xen 3.3.0 and now testing the pci pass-through with the NIC. Using late binding, the pci slot 0000:08:01.0 is assigned to pciback. But pci related xm commands are not working. For eg: linux-242:/home/xen-3.3.0 # xm pci-list-assignable-devices Unexpected error: <type ''exceptions.OSError''> Please report to

...in_vqs, **out_vqs; - /* Used for numbering devices for sysfs and debugfs */ - unsigned int drv_index; - /* Major number for this device. Ports will be created as minors. */ int chr_major; }; @@ -1415,7 +1409,7 @@ static int add_port(struct ports_device *portdev, u32 id) } port->dev = device_create(pdrvdata.class, &port->portdev->vdev->dev, devt, port, "vport%up%u", - port->portdev->drv_index, id); + port->portdev->vdev->index, id); if (IS_ERR(port->dev)) { err = PTR_ERR(port->dev); dev_err(&port->portdev->vdev...

...in_vqs, **out_vqs; - /* Used for numbering devices for sysfs and debugfs */ - unsigned int drv_index; - /* Major number for this device. Ports will be created as minors. */ int chr_major; }; @@ -1415,7 +1409,7 @@ static int add_port(struct ports_device *portdev, u32 id) } port->dev = device_create(pdrvdata.class, &port->portdev->vdev->dev, devt, port, "vport%up%u", - port->portdev->drv_index, id); + port->portdev->vdev->index, id); if (IS_ERR(port->dev)) { err = PTR_ERR(port->dev); dev_err(&port->portdev->vdev...

...v->vdpa = vdpa; > + v->nvqs = nvqs; > + v->virtio_id = ops->get_device_id(vdpa); > + > + mutex_lock(&vhost_vdpa.mutex); > + > + minor = vhost_vdpa_alloc_minor(v); > + if (minor < 0) { > + r = minor; > + goto err_alloc_minor; > + } > + > + d = device_create(vhost_vdpa.class, NULL, > + MKDEV(MAJOR(vhost_vdpa.devt), minor), > + v, "%d", vdpa->index); > + if (IS_ERR(d)) { > + r = PTR_ERR(d); > + goto err_device_create; > + } > + I can't understand what this messing around with major/minor numbers does....

...v->vdpa = vdpa; > + v->nvqs = nvqs; > + v->virtio_id = ops->get_device_id(vdpa); > + > + mutex_lock(&vhost_vdpa.mutex); > + > + minor = vhost_vdpa_alloc_minor(v); > + if (minor < 0) { > + r = minor; > + goto err_alloc_minor; > + } > + > + d = device_create(vhost_vdpa.class, NULL, > + MKDEV(MAJOR(vhost_vdpa.devt), minor), > + v, "%d", vdpa->index); > + if (IS_ERR(d)) { > + r = PTR_ERR(d); > + goto err_device_create; > + } > + I can't understand what this messing around with major/minor numbers does....

...+ v->virtio_id = ops->get_device_id(vdpa); > > + > > + mutex_lock(&vhost_vdpa.mutex); > > + > > + minor = vhost_vdpa_alloc_minor(v); > > + if (minor < 0) { > > + r = minor; > > + goto err_alloc_minor; > > + } > > + > > + d = device_create(vhost_vdpa.class, NULL, > > + MKDEV(MAJOR(vhost_vdpa.devt), minor), > > + v, "%d", vdpa->index); > > + if (IS_ERR(d)) { > > + r = PTR_ERR(d); > > + goto err_device_create; > > + } > > + > > I can't understand what this...

On Thu, Jun 12, 2014 at 05:08:37PM +0530, abhishek jain wrote: > Hi Rich > > I have all the virtio modules available in the kernel but I'm getting the > same result . It doesn't appear to be using any kernel modules. I would have expected to see output such as this: supermin: internal insmod virtio.ko It seems as if you might not be setting SUPERMIN_MODULES; or maybe you

..._bar); + mdev->aper.va = ioremap_wc(mdev->aper.pa, mdev->aper.len); + if (!mdev->aper.va) { + dev_err(&pdev->dev, "Cannot remap Aperture BAR\n"); + rc = -EIO; + goto unmap_mmio; + } + + mdev->ops->init(mdev); + + pci_set_drvdata(pdev, mdev); + + mdev->sdev = device_create(g_mic.mic_class, &pdev->dev, + MKDEV(MAJOR(g_mic.mdev_id), mdev->id), NULL, "%s", mdev->name); + if (IS_ERR(mdev->sdev)) { + rc = PTR_ERR(mdev->sdev); + dev_err(&pdev->dev, "device_create failed rc %d\n", rc); + goto unmap_aper; + } + + rc = sys...

...+ pr_err("%s: error registering chrdev region, ret = %d\n", + __func__, ret); + goto free_cdev; + } + ret = cdev_add(&port->cdev, devt, 1); + if (ret < 0) { + pr_err("%s: error adding cdev, ret = %d\n", __func__, ret); + goto free_cdev; + } + port->dev = device_create(virtserial.class, NULL, devt, NULL, + "vmch%u", port_nr); + if (IS_ERR(port->dev)) { + ret = PTR_ERR(port->dev); + pr_err("%s: Error creating device, ret = %d\n", __func__, ret); + goto free_cdev; + } + INIT_LIST_HEAD(&port->readbuf_head); + init_waitque...

...+ pr_err("%s: error registering chrdev region, ret = %d\n", + __func__, ret); + goto free_cdev; + } + ret = cdev_add(&port->cdev, devt, 1); + if (ret < 0) { + pr_err("%s: error adding cdev, ret = %d\n", __func__, ret); + goto free_cdev; + } + port->dev = device_create(virtserial.class, NULL, devt, NULL, + "vmch%u", port_nr); + if (IS_ERR(port->dev)) { + ret = PTR_ERR(port->dev); + pr_err("%s: Error creating device, ret = %d\n", __func__, ret); + goto free_cdev; + } + INIT_LIST_HEAD(&port->readbuf_head); + init_waitque...

...] virtio_ring: disagrees about version of symbol dev_err > [ 1.162845] virtio_ring: Unknown symbol dev_err (err -22) > insmod: init_module: virtio_ring.ko: Invalid parameters > supermin: internal insmod virtio_blk.ko > [ 1.167444] virtio_blk: disagrees about version of symbol > device_create_file > [ 1.169352] virtio_blk: Unknown symbol device_create_file (err -22) > [ 1.171105] virtio_blk: disagrees about version of symbol dev_notice > [ 1.172818] virtio_blk: Unknown symbol dev_notice (err -22) > insmod: init_module: virtio_blk.ko: Invalid parameters > supe...

Hey Rusty, These are the patches that rework a few bits to make hot-unplug while ports are open not crash apps (or kernels). The problem is when hot-unplug is performed when a port is open, the cdev struct is kept around by the file pointers and when the app later does a 'close', things go boom-boom. This patch series makes sure port as well as device hot-unplug is now safe to perform

Hey Rusty, These are the patches that rework a few bits to make hot-unplug while ports are open not crash apps (or kernels). The problem is when hot-unplug is performed when a port is open, the cdev struct is kept around by the file pointers and when the app later does a 'close', things go boom-boom. This patch series makes sure port as well as device hot-unplug is now safe to perform

...;vtvq->kaddbuf_list); + list_del(pos); + kfree(vtvq); + } + vdev->config->del_vqs(vdev); +} + +static int create_devno(dev_t *devno) +{ + struct device *dev; + char dev_name[DEV_NAME_MAX]; + + snprintf(dev_name, DEV_NAME_MAX, "%s%u", "viotest", MINOR(*devno)); + dev = device_create(viotest_class, NULL, *devno, NULL, dev_name); + if (IS_ERR(dev)) + return PTR_ERR(dev); + + return 0; +} + +static void reset_device(struct viotest_dev *vtest) +{ + struct viotest_vq *vtvq; + + BUG_ON(!(vtest->flags & CLEANUP_PENDING)); + + list_for_each_entry(vtvq, &vtest->vq_li...