similar to: [LLVMdev] Remove $SHS/vop to fix your build

Displaying 20 results from an estimated 30000 matches similar to: "[LLVMdev] Remove $SHS/vop to fix your build"

2016 Aug 01
1
[vhost:vhost 11/15] warning: (VOP && ..) selects VHOST_RING which has unmet direct dependencies (NETDEVICES && ..)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: c4ea43c2c1779f5dde3ff5645b830c90f75ccc15 commit: efd7eb77f631e1ed3533db7725df157a379c78ef [11/15] VSOCK: Add Makefile and Kconfig config: x86_64-randconfig-x005-201631 (attached as .config) compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705 reproduce: git checkout efd7eb77f631e1ed3533db7725df157a379c78ef
2016 Aug 01
1
[vhost:vhost 11/15] warning: (VOP && ..) selects VHOST_RING which has unmet direct dependencies (NETDEVICES && ..)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: c4ea43c2c1779f5dde3ff5645b830c90f75ccc15 commit: efd7eb77f631e1ed3533db7725df157a379c78ef [11/15] VSOCK: Add Makefile and Kconfig config: x86_64-randconfig-x005-201631 (attached as .config) compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705 reproduce: git checkout efd7eb77f631e1ed3533db7725df157a379c78ef
2007 Dec 30
1
Histogram with different colors for different portions
Dear Rusers, I would like to color different sections of a histogram different colors. I have an example that was done by "brute force" given below. Has anyone implemented something like this in general? If not, any suggestions/pointers on how to write a general function to do so would be most appreciated. Alan-
2019 Feb 26
0
[PATCH v2 char-misc-next 4/7] mic: vop: Add loopback driver
On Fri, Feb 22, 2019 at 04:30:52PM +0100, Vincent Whitchurch wrote: > Add a loopback driver to allow testing and evaluation of the VOP > framework without special hardware. The host and the guest will run > under the same kernel. > > Signed-off-by: Vincent Whitchurch <vincent.whitchurch at axis.com> > --- > drivers/misc/mic/Kconfig | 10 + >
2011 Jul 04
1
Contrastes con el paquete survey (svycontrast)
Estimados usuarios: Estoy intentando reproducir el ejemplo 6.4 de Thomas Lumley. Complex Survey. Editorial Wiley. 2010 (ver la página en google:
2017 Dec 12
1
[PATCH 2/3] virtio: use put_device instead of kfree
On Mon, 11 Dec 2017 23:55:26 +0800 weiping zhang <zhangweiping at didichuxing.com> wrote: > don't free vp_vdev until vp_vdev.dev.release be called. Same comment as for the virtio_pci patch. > > Signed-off-by: weiping zhang <zhangweiping at didichuxing.com> > --- > drivers/misc/mic/vop/vop_main.c | 16 +++++++++------- > 1 file changed, 9 insertions(+), 7
2017 Dec 12
1
[PATCH 2/3] virtio: use put_device instead of kfree
On Mon, 11 Dec 2017 23:55:26 +0800 weiping zhang <zhangweiping at didichuxing.com> wrote: > don't free vp_vdev until vp_vdev.dev.release be called. Same comment as for the virtio_pci patch. > > Signed-off-by: weiping zhang <zhangweiping at didichuxing.com> > --- > drivers/misc/mic/vop/vop_main.c | 16 +++++++++------- > 1 file changed, 9 insertions(+), 7
2017 Dec 12
5
[PATCH v2 0/3] fix cleanup for fail to register_virtio_device
This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. V1->V2: * virtio_pci: add comments for the reason use put_device * virtio vop: also use put_device in in _vop_remove_device() weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of
2017 Dec 12
5
[PATCH v2 0/3] fix cleanup for fail to register_virtio_device
This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. V1->V2: * virtio_pci: add comments for the reason use put_device * virtio vop: also use put_device in in _vop_remove_device() weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of
2016 Aug 01
0
[vhost:vhost 5/15] warning: (VOP && ..) selects VHOST_RING which has unmet direct dependencies (NETDEVICES && ..)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: ccbb911915b99ba9ff81a1cfa4f07c98f98fff83 commit: 4d167a33a6669c309f8fcdc6cd7143de3b5445b3 [5/15] vhost: drop vringh dependency config: x86_64-randconfig-x005-201631 (attached as .config) compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705 reproduce: git checkout 4d167a33a6669c309f8fcdc6cd7143de3b5445b3
2016 Aug 01
0
[vhost:vhost 5/15] warning: (VOP && ..) selects VHOST_RING which has unmet direct dependencies (NETDEVICES && ..)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost head: ccbb911915b99ba9ff81a1cfa4f07c98f98fff83 commit: 4d167a33a6669c309f8fcdc6cd7143de3b5445b3 [5/15] vhost: drop vringh dependency config: x86_64-randconfig-x005-201631 (attached as .config) compiler: gcc-6 (Debian 6.1.1-9) 6.1.1 20160705 reproduce: git checkout 4d167a33a6669c309f8fcdc6cd7143de3b5445b3
2017 Dec 11
6
[PATCH 0/3] fix cleanup for fail to register_virtio_device
This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of virtio_device.dev drivers/misc/mic/vop/vop_main.c | 16 +++++++++------- drivers/remoteproc/remoteproc_virtio.c | 2 +-
2017 Dec 11
6
[PATCH 0/3] fix cleanup for fail to register_virtio_device
This series fix the cleanup for the caller of register_virtio_device, the main work is use put_device instead of kfree. weiping zhang (3): virtio_pci: use put_device instead of kfree virtio: use put_device instead of kfree virtio: put reference count of virtio_device.dev drivers/misc/mic/vop/vop_main.c | 16 +++++++++------- drivers/remoteproc/remoteproc_virtio.c | 2 +-
2013 Oct 26
3
lpxelinux.0 - 6.02 - failed to load ldlinux.c32
Hello Geert Thanks for replying.. But i think i can?t use it, as i don?t reach the point where the debug module will be available.. it just pulls the lpxelinux.0 and tries to get the next download-- the ldlinux.c32 and it fails...and freezes. And the next step would be other modules i think.. if i?m wrong.. excuse me 8-).. yesterday i managed to get ipxelinux working from ipxe.org.. so the nic
2017 Dec 20
8
[PATCH v4 0/4] use put_device to cleanup resource
Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get
2017 Dec 20
8
[PATCH v4 0/4] use put_device to cleanup resource
Hi, The main change is split device_register into 2 sperate calls: device_initalize() and device_add, and then the caller can use put_device safety when fail to register_virtio_device. v3->v4: * split device_register into device_initialize and devicea_add that the caller can always use put_device when fail to register virtio device. v2->v3: * virtio: add new helper do get
2020 Apr 01
2
[PATCH V9 1/9] vhost: refine vhost and vringh kconfig
On Thu, Mar 26, 2020 at 10:01:17PM +0800, Jason Wang wrote: > Currently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost is > not necessarily for VM since it's a generic userspace and kernel > communication protocol. Such dependency may prevent archs without > virtualization support from using vhost. > > To solve this, a dedicated vhost menu is created under drivers
2020 Apr 01
2
[PATCH V9 1/9] vhost: refine vhost and vringh kconfig
On Thu, Mar 26, 2020 at 10:01:17PM +0800, Jason Wang wrote: > Currently, CONFIG_VHOST depends on CONFIG_VIRTUALIZATION. But vhost is > not necessarily for VM since it's a generic userspace and kernel > communication protocol. Such dependency may prevent archs without > virtualization support from using vhost. > > To solve this, a dedicated vhost menu is created under drivers
2013 Nov 05
1
[LLVMdev] Thread-safe cloning
Sorry to resurrect an old thread, but I finally got around to testing this approach (round tripping through bitcode in memory) and it works beautifully - and isn't that much slower than cloning. I have noticed however that the copy process isn't thread-safe. The problem is that in Function, there is lazy initialization code for arguments: void CheckLazyArguments() const { if
2011 Jun 01
2
[LLVMdev] How best to time passes using the API instead of opt? Also, memory leaks when trying to do timing in the API.
Thanks for the reply! Unfortunately, that seems to have the same effect as setting llvm::TimePassesIsEnabled myself, and all my same problems still apply as the TimingInfo's destructor (PassManager.cpp) is still never called. Running it in the debugger shows that TimerGroup's removeTimer method is never called, nor is it's destructor (but it's constructor is). On Wed, Jun 1, 2011