search for: iohandler

On 15 Feb 2018, at 15:45, Siegmar Gross via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > today I've tried to build llvm-6.0.0rc2 using Cmake on my "SUSE Linux > Enterprise Server 12.3 (x86_64)" with the following commands (gcc-6.4.0 > is necessary for CUDA-9.0). > > > wget http://prereleases.llvm.org/6.0.0/rc2/llvm-6.0.0rc2.src.tar.xz > wget

Hi, today I've tried to build llvm-6.0.0rc2 using Cmake on my "SUSE Linux Enterprise Server 12.3 (x86_64)" with the following commands (gcc-6.4.0 is necessary for CUDA-9.0). wget http://prereleases.llvm.org/6.0.0/rc2/llvm-6.0.0rc2.src.tar.xz wget http://prereleases.llvm.org/6.0.0/rc2/cfe-6.0.0rc2.src.tar.xz wget

...=override_context at entry=0x0, repeat_on_empty_command=repeat_on_empty_command at entry=true, no_context_switching=false) at /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:1820 #16 0x00007f103ceca50d in lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, std::string&) (this=0x7a5210, io_handler=..., line=...) at /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:2976 #17 0x00007f103ce1c733 in lldb_private::IOHandlerEditline::Run() (this=0x87d9b0)...

..., > repeat_on_empty_command=repeat_on_empty_command at entry=true, > no_context_switching=false) > at > /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:1820 > #16 0x00007f103ceca50d in > lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, > std::string&) (this=0x7a5210, io_handler=..., line=...) at > /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:2976 > #17 0x00007f103ce1c733 in lldb_private::IOHandlerEditline::Run() &gt...

...ty_command=repeat_on_empty_command at entry=true, >> no_context_switching=false) >> at >> /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:1820 >> #16 0x00007f103ceca50d in >> lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, >> std::string&) (this=0x7a5210, io_handler=..., line=...) at >> /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:2976 >> #17 0x00007f103ce1c733 in lldb_private::IOHandlerEditlin...

..._empty_command at entry=true, >>> no_context_switching=false) >>> at >>> /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:1820 >>> #16 0x00007f103ceca50d in >>> lldb_private::CommandInterpreter::IOHandlerInputComplete(lldb_private::IOHandler&, >>> std::string&) (this=0x7a5210, io_handler=..., line=...) at >>> /home/engshare/third-party2/lldb/3.8.0.rc3/src/llvm/tools/lldb/source/Interpreter/CommandInterpreter.cpp:2976 >>> #17 0x00007f103ce1c733 in lldb_private::IOHa...

..._notify_vq (vq=0x1b23740) at > /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:720 > #4 0x00000000006edf65 in virtio_queue_host_notifier_read (n=0x1b23790) > at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:1116 > #5 0x00000000005d3c9c in qemu_iohandler_poll (pollfds=0x1aae200, ret=1) > at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/iohandler.c:143 > #6 0x00000000005d4702 in main_loop_wait (nonblocking=0) at > /usr/src/debug/app-emulation/qemu-9999/qemu-9999/main-loop.c:484 > #7 0x000000000066c583 in main_loop () at > /usr/sr...

...(req=<optimized out>) at /opt/new/tools/qemu-xen-dir/xen-all.c:736 #5 handle_ioreq (req=0x7f94fa464000) at /opt/new/tools/qemu-xen-dir/xen-all.c:793 #6 0x00007f94fa748abe in cpu_handle_ioreq (opaque=0x7f94fb39d3f0) at /opt/new/tools/qemu-xen-dir/xen-all.c:868 #7 0x00007f94fa5e3262 in qemu_iohandler_poll (readfds=0x7f94faeea7a0 <rfds>, writefds=0x7f94faeea820 <wfds>, xfds=<optimized out>, ret=<optimized out>) at iohandler.c:125 #8 0x00007f94fa5ec51d in main_loop_wait (nonblocking=<optimized out>) at main-loop.c:418 #9 0x00007f94fa6616dc in main_loop () at vl.c:1...

...c4b5 in virtio_queue_notify_vq (vq=0x1b23740) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:720 #4 0x00000000006edf65 in virtio_queue_host_notifier_read (n=0x1b23790) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:1116 #5 0x00000000005d3c9c in qemu_iohandler_poll (pollfds=0x1aae200, ret=1) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/iohandler.c:143 #6 0x00000000005d4702 in main_loop_wait (nonblocking=0) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/main-loop.c:484 #7 0x000000000066c583 in main_loop () at /usr/src/debug/app-emulation/qem...

...c4b5 in virtio_queue_notify_vq (vq=0x1b23740) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:720 #4 0x00000000006edf65 in virtio_queue_host_notifier_read (n=0x1b23790) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/hw/virtio/virtio.c:1116 #5 0x00000000005d3c9c in qemu_iohandler_poll (pollfds=0x1aae200, ret=1) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/iohandler.c:143 #6 0x00000000005d4702 in main_loop_wait (nonblocking=0) at /usr/src/debug/app-emulation/qemu-9999/qemu-9999/main-loop.c:484 #7 0x000000000066c583 in main_loop () at /usr/src/debug/app-emulation/qem...

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_driver.c | 2293 +++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_driver.h | 48 + 2 files changed, 2341 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_driver.c create mode 100644 drivers/misc/vmw_vmci/vmci_driver.h diff --git

Signed-off-by: George Zhang <georgezhang at vmware.com> --- drivers/misc/vmw_vmci/vmci_driver.c | 2293 +++++++++++++++++++++++++++++++++++ drivers/misc/vmw_vmci/vmci_driver.h | 48 + 2 files changed, 2341 insertions(+), 0 deletions(-) create mode 100644 drivers/misc/vmw_vmci/vmci_driver.c create mode 100644 drivers/misc/vmw_vmci/vmci_driver.h diff --git

The following series of 10 patches is a merge of the xenfb and xenconsoled functionality into the qemu-dm code. The general approach taken is to have qemu-dm provide two machine types - one for xen paravirt, the other for fullyvirt. For compatability the later is the default. The goals overall are to kill LibVNCServer, remove alot of code duplication and/or parallel impls of the same concepts, and

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

Second revision of the VMware VMCI RFC patchset. It incorperates fixes for all the feedback about the comment blocks and style and now passes checkpatch with 0 errors and 0 warnings. Thanks to all who have reviewed the code thus far. * * * In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.

In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the Virtual Machine Communication Interface (vmw_vmci) and VMCI Sockets (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vmci kernel module. The vmw_vsock kernel module will be presented in a later post.