Linux Virtualization - Mar 2019

Saturday March 30 2019
TimeRepliesSubject
11:20AM 1 [PATCH 2/5] x86: Convert some slow-path static_cpu_has() callers to boot_cpu_has()
 
Friday March 29 2019
TimeRepliesSubject
10:31PM 0 [PATCH net v4] failover: allow name change on IFF_UP slave interfaces
3:15PM 1 [PATCH net v4] failover: allow name change on IFF_UP slave interfaces
1:45PM 0 [PATCH net v4] failover: allow name change on IFF_UP slave interfaces
5:55AM 0 [PATCH net v4] failover: allow name change on IFF_UP slave interfaces
 
Thursday March 28 2019
TimeRepliesSubject
7:49PM 0 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
5:14PM 0 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
12:06PM 1 [PATCH] MAINTAINERS: Update PARAVIRT_OPS_INTERFACE and VMWARE_HYPERVISOR_INTERFACE
10:32AM 0 [PATCH v2 -next] drm/virtio: remove set but not used variable 'vgdev'
 
Wednesday March 27 2019
TimeRepliesSubject
11:40PM 1 [RFC PATCH 00/68] VFS: Convert a bunch of filesystems to the new mount API
10:16PM 0 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
4:57PM 0 [PATCH] MAiNTAINERS: add Paolo, Stefan for virtio blk/scsi
3:08PM 0 [PATCH] MAiNTAINERS: add Paolo, Stefan for virtio blk/scsi
2:47PM 0 [PATCH v2 -next] drm/virtio: remove set but not used variable 'vgdev'
2:33PM 5 [PATCH] MAiNTAINERS: add Paolo, Stefan for virtio blk/scsi
11:11AM 0 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
10:36AM 0 [PATCH 2/2] scsi: virtio_scsi: limit number of hw queues by nr_cpu_ids
10:36AM 0 [PATCH 1/2] virtio-blk: limit number of hw queues by nr_cpu_ids
10:36AM 6 [PATCH 0/2] Limit number of hw queues by nr_cpu_ids for virtio-blk and virtio-scsi
2:13AM 2 [PATCH net v3] failover: allow name change on IFF_UP slave interfaces
 
Tuesday March 26 2019
TimeRepliesSubject
4:53PM 0 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
10:28AM 1 INFO: task hung in vhost_net_stop_vq
10:17AM 0 INFO: task hung in vhost_net_stop_vq
 
Monday March 25 2019
TimeRepliesSubject
6:03PM 2 [PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
4:40PM 0 [PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
3:57PM 2 [PATCH] x86/paravirt: Guard against invalid cpu # in pv_vcpu_is_preempted()
2:02PM 2 INFO: task hung in vhost_net_stop_vq
11:35AM 0 [PATCH v2 -next] drm/virtio: remove set but not used variable 'vgdev'
9:02AM 0 [PATCH -next] drm/ttm: remove set but not used variable 'vgdev'
12:57AM 1 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
 
Saturday March 23 2019
TimeRepliesSubject
9:01PM 0 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
 
Friday March 22 2019
TimeRepliesSubject
12:05AM 3 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
 
Thursday March 21 2019
TimeRepliesSubject
5:12PM 0 [summary] virtio network device failover writeup
4:31PM 1 [summary] virtio network device failover writeup
3:50PM 2 [summary] virtio network device failover writeup
3:45PM 0 [summary] virtio network device failover writeup
3:15PM 0 [summary] virtio network device failover writeup
2:49PM 0 [PATCH net v2] failover: allow name change on IFF_UP slave interfaces
2:41PM 0 [PATCH] VMCI/VSOCK: Add maintainers for VMCI, AF_VSOCK and VMCI transport
2:20PM 0 [PATCH net v2] failover: allow name change on IFF_UP slave interfaces
2:16PM 1 [summary] virtio network device failover writeup
2:04PM 2 [PATCH net v2] failover: allow name change on IFF_UP slave interfaces
1:51PM 0 [summary] virtio network device failover writeup
1:25PM 2 [summary] virtio network device failover writeup
1:12PM 0 [summary] virtio network device failover writeup
1:04PM 4 [summary] virtio network device failover writeup
12:57PM 0 [summary] virtio network device failover writeup
12:48PM 3 [summary] virtio network device failover writeup
12:37PM 0 [summary] virtio network device failover writeup
10:08AM 2 [summary] virtio network device failover writeup
8:58AM 0 [summary] virtio network device failover writeup
3:02AM 0 [PATCH net v2] failover: allow name change on IFF_UP slave interfaces
 
Wednesday March 20 2019
TimeRepliesSubject
10:19PM 2 [summary] virtio network device failover writeup
10:10PM 0 [summary] virtio network device failover writeup
9:44PM 2 [summary] virtio network device failover writeup
9:17PM 0 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
4:13PM 2 [RFC PATCH] virtio_ring: Use DMA API if guest memory is encrypted
2:09PM 0 [summary] virtio network device failover writeup
12:53PM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
12:23PM 2 [summary] virtio network device failover writeup
10:25AM 0 [summary] virtio network device failover writeup
8:51AM 0 [PATCH] drm/virtio: make resource id workaround runtime switchable.
8:36AM 1 [PATCH] drm/virtio: add virtio-gpu-features debugfs file.
 
Tuesday March 19 2019
TimeRepliesSubject
11:26PM 1 [summary] virtio network device failover writeup
9:19PM 2 [summary] virtio network device failover writeup
9:06PM 0 [summary] virtio network device failover writeup
3:46PM 0 [summary] virtio network device failover writeup
12:38PM 2 [summary] virtio network device failover writeup
6:04AM 0 [PATCH] virtio_console: initialize vtermno value for ports
2:22AM 3 virtio-blk: should num_vqs be limited by num_possible_cpus()?
 
Monday March 18 2019
TimeRepliesSubject
11:35AM 0 [PATCH v2 5/6] drm/virtio: drop fencing in virtio_gpu_resource_create_ioctl
11:33AM 1 [PATCH v3 5/5] drm/virtio: rework resource creation workflow.
11:33AM 0 [PATCH v3 4/5] drm/virtio: params struct for virtio_gpu_cmd_create_resource_3d()
11:33AM 0 [PATCH v3 3/5] drm/virtio: params struct for virtio_gpu_cmd_create_resource()
11:33AM 1 [PATCH v3 2/5] drm/virtio: use struct to pass params to virtio_gpu_object_create()
11:33AM 0 [PATCH v3 1/5] drm/virtio: move virtio_gpu_object_{attach, detach} calls.
7:47AM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
6:56AM 1 [PATCH] virtio_net: remove hcpu from virtnet_clean_affinity
 
Sunday March 17 2019
TimeRepliesSubject
1:55PM 3 [summary] virtio network device failover writeup
 
Friday March 15 2019
TimeRepliesSubject
12:41PM 2 virtio-blk: should num_vqs be limited by num_possible_cpus()?
4:50AM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
 
Thursday March 14 2019
TimeRepliesSubject
7:33PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
4:08PM 1 [PATCH 00/38] VFS: Convert trivial filesystems and more
1:49PM 2 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
12:32PM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
12:13PM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
10:42AM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
6:12AM 4 virtio-blk: should num_vqs be limited by num_possible_cpus()?
 
Wednesday March 13 2019
TimeRepliesSubject
5:49PM 1 [RFC] vhost: select TAP if VHOST is configured
4:05PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
9:39AM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
3:26AM 2 virtio-blk: should num_vqs be limited by num_possible_cpus()?
 
Tuesday March 12 2019
TimeRepliesSubject
10:50PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
9:53PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
9:11PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
8:04PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
5:33PM 0 virtio-blk: should num_vqs be limited by num_possible_cpus()?
5:22PM 4 virtio-blk: should num_vqs be limited by num_possible_cpus()?
8:01AM 0 [PATCH] virtio_ring: Fix potential mem leak in virtqueue_add_indirect_packed
7:51AM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
7:17AM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
3:52AM 9 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
3:50AM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:59AM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
2:56AM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:52AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
1:31AM 2 [PATCH 1/1] virtio_blk: replace 0 by HCTX_TYPE_DEFAULT to index blk_mq_tag_set->map
 
Monday March 11 2019
TimeRepliesSubject
10:38PM 0 [PATCH] VMCI: Use BIT() macro for bit definitions
6:48PM 0 [PATCH] drm/bochs: Fix NULL dereference on atomic_disable helper
6:14PM 4 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
5:02PM 0 [PATCH 0/5] Clean up TTM mmap offsets
5:00PM 0 [PATCH 0/5] Clean up TTM mmap offsets
4:39PM 0 [PATCH 0/5] Clean up TTM mmap offsets
1:59PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
1:43PM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
1:23PM 0 [PATCH] drm/bochs: Fix NULL dereference on atomic_disable helper
1:07PM 3 [PATCH] drm/bochs: Fix NULL dereference on atomic_disable helper
12:48PM 4 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:40AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:18AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:13AM 2 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
6:35AM 0 [PATCH] virtio_console: free unused buffers with virtio port
6:22AM 0 [PATCH] drm/bochs: Fix NULL dereference on atomic_disable helper
5:58AM 0 [PATCH] virtio_console: free unused buffers with virtio port
 
Sunday March 10 2019
TimeRepliesSubject
3:44AM 0 [PULL] virtio,vhost: cleanups and fixes
 
Saturday March 9 2019
TimeRepliesSubject
11:19PM 0 [PATCH] vhost: silence an unused-variable warning
 
Friday March 8 2019
TimeRepliesSubject
7:48PM 3 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:11PM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:58PM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:12PM 0 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
12:56PM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
9:15AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
9:13AM 2 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
8:58AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
8:50AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
3:45AM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
3:43AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
3:41AM 2 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
3:16AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:55AM 2 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:21AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
 
Thursday March 7 2019
TimeRepliesSubject
9:27PM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
8:17PM 3 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:38PM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:17PM 5 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:16PM 3 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:09PM 1 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
5:56PM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
4:37PM 0 [PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
3:47PM 3 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
3:34PM 3 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
4:13AM 0 [PATCH net v2] failover: allow name change on IFF_UP slave interfaces
2:45AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
2:42AM 0 [RFC PATCH V2 4/5] vhost: introduce helpers to get the size of metadata area
2:40AM 0 [RFC PATCH V2 4/5] vhost: introduce helpers to get the size of metadata area
2:38AM 0 [RFC PATCH V2 2/5] vhost: fine grain userspace memory accessors
 
Wednesday March 6 2019
TimeRepliesSubject
11:36PM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
9:36PM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
5:02PM 0 [PATCH] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
4:31PM 2 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
12:04PM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
11:05AM 1 [PATCH] vhost: silence an unused-variable warning
10:56AM 1 [RFC PATCH V2 4/5] vhost: introduce helpers to get the size of metadata area
10:45AM 1 [RFC PATCH V2 2/5] vhost: fine grain userspace memory accessors
10:13AM 2 [PATCH v2] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
9:10AM 2 [PATCH] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
8:41AM 0 [PATCH] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
8:12AM 0 [PATCH] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
7:23AM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
7:18AM 0 [RFC PATCH V2 5/5] vhost: access vq metadata through kernel virtual address
7:18AM 0 [RFC PATCH V2 4/5] vhost: introduce helpers to get the size of metadata area
7:18AM 0 [RFC PATCH V2 2/5] vhost: fine grain userspace memory accessors
7:18AM 12 [RFC PATCH V2 0/5] vhost: accelerate metadata access through vmap()
6:43AM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
12:36AM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
12:06AM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
 
Tuesday March 5 2019
TimeRepliesSubject
8:28PM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
7:24PM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
6:07PM 4 [PATCH] vsock/virtio: fix kernel panic from virtio_transport_reset_no_sock
7:09AM 2 [PATCH] virtio_console: free unused buffers with virtio port
2:33AM 0 [RFC PATCH net-next] failover: allow name change on IFF_UP slave interfaces
2:04AM 0 [RFC PATCH net] failover: allow name change on IFF_UP slave interfaces
 
Monday March 4 2019
TimeRepliesSubject
7:25PM 0 [PATCH] virtio_console: free unused buffers with virtio port
1:05PM 5 [PATCH] virtio_console: free unused buffers with virtio port
 
Friday March 1 2019
TimeRepliesSubject
1:27PM 0 [virtio-dev] Re: net_failover slave udev renaming (was Re: [RFC PATCH net-next v6 4/4] netvsc: refactor notifier/event handling code to use the bypass framework)
9:25AM 0 [PATCH v7 3/4] drm/qxl: remove conflicting framebuffers earlier
5:51AM 0 [PATCH] drm/virtio: Allow userspace to mmap() framebuffer
1:05AM 1 [virtio-dev] Re: net_failover slave udev renaming (was Re: [RFC PATCH net-next v6 4/4] netvsc: refactor notifier/event handling code to use the bypass framework)
12:20AM 0 [virtio-dev] Re: net_failover slave udev renaming (was Re: [RFC PATCH net-next v6 4/4] netvsc: refactor notifier/event handling code to use the bypass framework)