search for: autobind

Hi, I have been trying to figure out how pid namespaces interact with netlink. netlink uses pids (or really tids I hope?) to address sockets associated with processes. The netlink code passes around pids without caring much about the pid namespace. It does pass around some information about the network namespace, but that doesn't help here because the pid namespace is not necessarily

Hi, I have been trying to figure out how pid namespaces interact with netlink. netlink uses pids (or really tids I hope?) to address sockets associated with processes. The netlink code passes around pids without caring much about the pid namespace. It does pass around some information about the network namespace, but that doesn't help here because the pid namespace is not necessarily

...cards: 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06) 01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M2000M] (rev a2) The internal display is connected to the Intel card. External display ports are wired to the NVIDIA card. I'm using the autobind-GPUs Xorg patch so that I don't have to run `xrandr --setprovideroutputsource` in order to make the external ports usable. While I'm away from the system, the monitor gets blanked. While it's in this state, I see many change events from the NVIDIA device (udevadm monitor output attache...

> -----Original Message----- > From: Alex Williamson [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 > >

> -----Original Message----- > From: Alex Williamson [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 > >

...ert autoAnswer from esxVI_Boolean to a simple bool (Matthias Bolte) - esx: Fix race condition in esxVI_EnsureSession (Matthias Bolte) - esx: Whitespace cleanup in the generator (Matthias Bolte) - esx: Change some alignments in the input file (Matthias Bolte) - esx: Change generated method parameter autobinding (Matthias Bolte) - virsh: Report an error when virGetUserDirectory fails (Matthias Bolte) - maint: mark more perl scripts executable (Eric Blake) - maint: mark perl script executable (Eric Blake) - maint: ignore generated file (Eric Blake) - Improve error message when XDR marshalling fails (Dani...

The current code for primitive splitting and emission on pre-nv50 is severely broken. In particular: 1. Quads and lines are totally broken because "&= 3" should be "&= ~3" and similar for lines 2. Triangle fans and polygons are broken because the first vertex must be repeated for each split chunk 3. Line loops are broken because the must be converted to a line strip,

- This avoids problematic "reloc'ed while mapped" messages and some associated corruption as well. Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++ src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++ src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++

From: Andy King <acking at vmware.com> ** Introduce VM Sockets *** In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly VMCI Sockets) (vmw_vsock) kernel module for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. Unlike previous

From: Andy King <acking at vmware.com> ** Introduce VM Sockets *** In an effort to improve the out-of-the-box experience with Linux kernels for VMware users, VMware is working on readying the VM Sockets (VSOCK, formerly VMCI Sockets) (vmw_vsock) kernel module for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. Unlike previous

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware to address Greg's and all other's code review comments. Summary of changes: - Rebase our linux kernel tree from v3.5 to v3.7. - Fix all checkpatch warnings and errors. Fix some checkpatch with -strict errors. This addresses Greg's comment: On 15 Nov 2012

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware. Summary of changes: - Sparse clean. - Checkpatch clean with one exception, a "complex macro" in which we can't add parentheses. - Remove all runtime assertions. - Fix device name, so that existing user clients work. - Fix VMCI handle lookup. * *

* * * This series of VSOCK linux upstreaming patches include latest udpate from VMware. Summary of changes: - Sparse clean. - Checkpatch clean with one exception, a "complex macro" in which we can't add parentheses. - Remove all runtime assertions. - Fix device name, so that existing user clients work. - Fix VMCI handle lookup. * *

* * * 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 (VSOCK) (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. The vmw_vmci kernel module has been presented in

* * * 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 (VSOCK) (vmw_vsock) kernel modules for inclusion in the Linux kernel. The purpose of this post is to acquire feedback on the vmw_vsock kernel module. The vmw_vmci kernel module has been presented in