search for: unbind

...as count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 mtrr: reg: 3 has count=0 At XFree86.log this are the last menssages: (II) I810(0): xf86UnbindGARTMemory: unbind key 7 (II) I810(0): xf86UnbindGARTMemory: unbind key 0 (II) I810(0): xf86UnbindGARTMemory: unbind key 2 (II) I810(0): xf86UnbindGARTMemory: unbind key 1 (II) I810(0): xf86UnbindGARTMemory: unbind key 3 (II) I810(0): xf86UnbindGARTMemory: unbind key 4 (II) I810(0): xf86UnbindGARTMe...

...id not make a difference, here's how the output looks now; Sat Nov 1 17:07:03 2014 <5> ulogd.c:843 building new pluginstance stack: 'log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU' Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 2 Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 10 Sat Nov 1 17:07:03 2014 <5> ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 7 Sat Nov 1 17:07:03 2014 <3&...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that i...

Alex, I'm trying to think through how binding/unbinding of devices will work with VFIO for platform devices and have a couple of questions about how vfio-pci works. When you bind a device to vfio-pci, e.g.: # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id ...I understand that the echo into 'new_id' tells the vfio pci driver that i...

On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > Alex, > > I'm trying to think through how binding/unbinding of devices will > work with VFIO for platform devices and have a couple of questions > about how vfio-pci works. > > When you bind a device to vfio-pci, e.g.: > # echo 1102 0002 > /sys/bus/pci/drivers/vfio-pci/new_id > > ...I understand that the echo into 'new_id...

...[mailto:alex.williamson at redhat.com] > Sent: Tuesday, July 02, 2013 9:46 AM > To: Yoder Stuart-B08248 > Cc: kvm at vger.kernel.org list; Alexander Graf; Bhushan Bharat-R65777; a.motakis at virtualopensystems.com; > virtualization at lists.linux-foundation.org > Subject: Re: binding/unbinding devices to vfio-pci > > On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > > Alex, > > > > I'm trying to think through how binding/unbinding of devices will > > work with VFIO for platform devices and have a couple of questions > > about how...

...[mailto:alex.williamson at redhat.com] > Sent: Tuesday, July 02, 2013 9:46 AM > To: Yoder Stuart-B08248 > Cc: kvm at vger.kernel.org list; Alexander Graf; Bhushan Bharat-R65777; a.motakis at virtualopensystems.com; > virtualization at lists.linux-foundation.org > Subject: Re: binding/unbinding devices to vfio-pci > > On Tue, 2013-07-02 at 14:15 +0000, Yoder Stuart-B08248 wrote: > > Alex, > > > > I'm trying to think through how binding/unbinding of devices will > > work with VFIO for platform devices and have a couple of questions > > about how...

Hi all, I have a data.frame I received with data that look like this (comma separated strings in last row): ID Shop Items ID1 A1 item1, item2, item3 ID2 A2 item4, item5 ID3 A1 item1, item3, item4 But I would like to unbind the strings in col(2) items so that it will look like this: ID Shop Items ID1 A1 item1 ID1 A1 item2 ID1 A1 item3 ID2 A2 item4 ID2 A2 item5 ID3 A1 item1 ID3 A1 item3 ID3 A1 item4 Meaning each item is on a different row but still maintain the ties with the IDs and the Shops. The final purpose is t...

...drm/virtio/virtgpu_ttm.c @@ -319,7 +319,7 @@ static void virtio_gpu_ttm_backend_destroy(struct ttm_tt *ttm) kfree(gtt); } -static struct ttm_backend_func virtio_gpu_backend_func = { +static const struct ttm_backend_func virtio_gpu_backend_func = { .bind = &virtio_gpu_ttm_backend_bind, .unbind = &virtio_gpu_ttm_backend_unbind, .destroy = &virtio_gpu_ttm_backend_destroy, diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c index e343074..9fa758c 100644 --- a/drivers/gpu/drm/radeon/radeon_ttm.c +++ b/drivers/gpu/drm/radeon/radeon_ttm.c @@ -666,7...

...drm/virtio/virtgpu_ttm.c @@ -319,7 +319,7 @@ static void virtio_gpu_ttm_backend_destroy(struct ttm_tt *ttm) kfree(gtt); } -static struct ttm_backend_func virtio_gpu_backend_func = { +static const struct ttm_backend_func virtio_gpu_backend_func = { .bind = &virtio_gpu_ttm_backend_bind, .unbind = &virtio_gpu_ttm_backend_unbind, .destroy = &virtio_gpu_ttm_backend_destroy, diff --git a/drivers/gpu/drm/radeon/radeon_ttm.c b/drivers/gpu/drm/radeon/radeon_ttm.c index e343074..9fa758c 100644 --- a/drivers/gpu/drm/radeon/radeon_ttm.c +++ b/drivers/gpu/drm/radeon/radeon_ttm.c @@ -666,7...

...lude <linux/module.h> #include <linux/console.h> +#include <linux/vt_kern.h> #include <drm/drmP.h> #include <drm/drm.h> @@ -89,6 +90,11 @@ qxl_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) drm_kms_helper_poll_init(&qdev->ddev); + /* unbind vgacon to make sure it doesn't touch our vga registers */ + console_lock(); + ret = do_take_over_console(&dummy_con, 0, MAX_NR_CONSOLES - 1, true); + console_unlock(); + /* Complete initialization. */ ret = drm_dev_register(&qdev->ddev, ent->driver_data); if (ret) -- 2.9.3

...lude <linux/module.h> #include <linux/console.h> +#include <linux/vt_kern.h> #include <drm/drmP.h> #include <drm/drm.h> @@ -89,6 +90,11 @@ qxl_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) drm_kms_helper_poll_init(&qdev->ddev); + /* unbind vgacon to make sure it doesn't touch our vga registers */ + console_lock(); + ret = do_take_over_console(&dummy_con, 0, MAX_NR_CONSOLES - 1, true); + console_unlock(); + /* Complete initialization. */ ret = drm_dev_register(&qdev->ddev, ent->driver_data); if (ret) -- 2.9.3

My bad; I did test suspend/resume, but not unbinding. Shouldn’t that happen on shutdown as well, as the driver gets unloaded? I don’t remember seeing that issue there though. On 2018-02-17 — 13:40, Lukas Wunner wrote: > Unbinding nouveau on a dual GPU MacBook Pro oopses because we iterate > over the bl_connectors list in nouveau_backlight_e...

Unbinding nouveau on a dual GPU MacBook Pro oopses because we iterate over the bl_connectors list in nouveau_backlight_exit() but skipped initializing it in nouveau_backlight_init(). Stacktrace for posterity: BUG: unable to handle kernel NULL pointer dereference at 0000000000000010 IP: nouveau_b...

On Mon, Feb 19, 2018 at 10:38:04AM +0100, Pierre Moreau wrote: > On 2018-02-17 13:40, Lukas Wunner wrote: > > Unbinding nouveau on a dual GPU MacBook Pro oopses because we iterate > > over the bl_connectors list in nouveau_backlight_exit() but skipped > > initializing it in nouveau_backlight_init(). > > --- a/drivers/gpu/drm/nouveau/nouveau_backlight.c > > +++ b/drivers/gpu/drm/nouveau/nou...

...up 1 which I believe is what you said I need. And now with this setting I'm seeing logging... :) In ulog.conf I'm using; stack=log2:NFLOG,base1:BASE,ifi1:IFINDEX,ip2str1:IP2STR,print1:PRINTPKT,emu1:LOGEMU But I noticed I was still getting these messages; ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 2 ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 7 ulogd_inppkt_NFLOG.c:503 forcing unbind of existing log handler for protocol 10 And I noticed that if I commentd out #bind=1 under [log2] then these messages don't appear; ```...

Hi all I have a very weird case of pci passthrough. I have a machine with 7 network interfaces, all of them intel. Four of them are on one quad giga ethernet device. If I manually unbind the devices and allow qemu to use them, with intel IOMMU working, everything works like a charm. Here's how I do it manually: root@kybrat (x86_64) ~]$ lspci -nn | grep net 00:19.0 Ethernet controller [0200]: Intel Corporation 82579V Gigabit Network Connection [8086:1503] (rev 06) 02:00.0 Ethe...

Hi all, I want to do live migration of domains using DRBD block devices for synchronisation between the two Xen hosts with Xen 2.0.7. I''ve written a script ( block-drbd ) which binds / unbinds DRBD devices for specific domains (with DRBD, only one host can write on a drbd device at the same time). This script sets the current host as master (bind) or secondary (unbind) in a DRBD "Netword-RAID" Bringing up a domain works fine. But when I try to migrate it ( live with -l fl...

On Mon, Feb 19, 2018 at 10:38:04AM +0100, Pierre Moreau wrote: > My bad; I did test suspend/resume, but not unbinding. Shouldn???t that > happen on shutdown as well, as the driver gets unloaded? I don???t remember > seeing that issue there though. Sorry Pierre, I missed this question and am seeing it only now on saving the message away: On shutdown the driver isn't unloaded, rather the driver core w...

...ux/console.h> > +#include <linux/vt_kern.h> > > #include <drm/drmP.h> > #include <drm/drm.h> > @@ -89,6 +90,11 @@ qxl_pci_probe(struct pci_dev *pdev, const struct pci_device_id *ent) > > drm_kms_helper_poll_init(&qdev->ddev); > > + /* unbind vgacon to make sure it doesn't touch our vga registers */ > + console_lock(); > + ret = do_take_over_console(&dummy_con, 0, MAX_NR_CONSOLES - 1, true); > + console_unlock(); Still seems very late, in i915 we kick out vgacon as pretty much the first thing in driver load. See i915_k...