similar to: virtio for 3.20

Displaying 20 results from an estimated 40000 matches similar to: "virtio for 3.20"

2015 Jan 21
2
virtio for 3.20
On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Hi Rusty, all > > > > I parked outstanding virtio patches here: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > > this way they are merged in linux-next as well. > > > > Rusty if you'll be
2015 Jan 21
2
virtio for 3.20
On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: > "Michael S. Tsirkin" <mst at redhat.com> writes: > > Hi Rusty, all > > > > I parked outstanding virtio patches here: > > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > > this way they are merged in linux-next as well. > > > > Rusty if you'll be
2015 Jan 22
0
virtio for 3.20
"Michael S. Tsirkin" <mst at redhat.com> writes: > On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: >> "Michael S. Tsirkin" <mst at redhat.com> writes: >> > Hi Rusty, all >> > >> > I parked outstanding virtio patches here: >> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next >>
2015 Jan 22
0
virtio for 3.20
"Michael S. Tsirkin" <mst at redhat.com> writes: > On Mon, Jan 19, 2015 at 12:56:28PM +1030, Rusty Russell wrote: >> "Michael S. Tsirkin" <mst at redhat.com> writes: >> > Hi Rusty, all >> > >> > I parked outstanding virtio patches here: >> > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next >>
2015 Jan 19
0
virtio for 3.20
"Michael S. Tsirkin" <mst at redhat.com> writes: > Hi Rusty, all > > I parked outstanding virtio patches here: > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > this way they are merged in linux-next as well. > > Rusty if you'll be doing 3.20 window, would you mind > checking that tree to verify nothing's lost? Hi Michael,
2015 Jan 19
0
virtio for 3.20
"Michael S. Tsirkin" <mst at redhat.com> writes: > Hi Rusty, all > > I parked outstanding virtio patches here: > git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next > this way they are merged in linux-next as well. > > Rusty if you'll be doing 3.20 window, would you mind > checking that tree to verify nothing's lost? Hi Michael,
2023 Mar 23
2
[PATCH 1/1] vhost_task: Fix vhost_task_create return value
On Thu, Mar 23, 2023 at 12:50:49PM +0100, Christian Brauner wrote: > On Thu, Mar 23, 2023 at 07:43:04AM -0400, Michael S. Tsirkin wrote: > > On Thu, Mar 23, 2023 at 11:44:45AM +0100, Christian Brauner wrote: > > > On Thu, Mar 23, 2023 at 03:37:19AM -0400, Michael S. Tsirkin wrote: > > > > On Wed, Mar 22, 2023 at 01:56:05PM -0500, Mike Christie wrote: > > >
2013 Mar 13
1
vhost questions.
OK, I've been trying to read the vhost and vhost net code, and I'm struggling with basic questions. 1) Why do we allow userspace to change an already-set-up vhost device? Why not have: open() ioctl(VHOST_GET_FEATURES) ioctl(VHOST_SET_VRING) x n (sets num, addresses, kick/call/err fds) ioctl(VHOST_NET_SETUP) ... close() You're not
2013 Mar 13
1
vhost questions.
OK, I've been trying to read the vhost and vhost net code, and I'm struggling with basic questions. 1) Why do we allow userspace to change an already-set-up vhost device? Why not have: open() ioctl(VHOST_GET_FEATURES) ioctl(VHOST_SET_VRING) x n (sets num, addresses, kick/call/err fds) ioctl(VHOST_NET_SETUP) ... close() You're not
2010 Dec 13
3
[GIT PULL net-next-2.6] vhost-net: tools, cleanups, optimizations
Please merge the following tree for 2.6.38. Thanks! The following changes since commit ad1184c6cf067a13e8cb2a4e7ccc407f947027d0: net: au1000_eth: remove unused global variable. (2010-12-11 12:01:48 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next Jason Wang (1): vhost: fix typos in comment Julia Lawall (1):
2010 Dec 13
3
[GIT PULL net-next-2.6] vhost-net: tools, cleanups, optimizations
Please merge the following tree for 2.6.38. Thanks! The following changes since commit ad1184c6cf067a13e8cb2a4e7ccc407f947027d0: net: au1000_eth: remove unused global variable. (2010-12-11 12:01:48 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-net-next Jason Wang (1): vhost: fix typos in comment Julia Lawall (1):
2020 May 05
3
[vhost:vhost 8/22] drivers/virtio/virtio_mem.c:1375:20: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'?
On Tue, May 05, 2020 at 05:46:44PM +0200, David Hildenbrand wrote: > On 05.05.20 17:44, Michael S. Tsirkin wrote: > > On Tue, May 05, 2020 at 04:50:13PM +0200, David Hildenbrand wrote: > >> On 05.05.20 16:15, kbuild test robot wrote: > >>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost > >>> head:
2020 May 05
3
[vhost:vhost 8/22] drivers/virtio/virtio_mem.c:1375:20: error: implicit declaration of function 'kzalloc'; did you mean 'vzalloc'?
On Tue, May 05, 2020 at 05:46:44PM +0200, David Hildenbrand wrote: > On 05.05.20 17:44, Michael S. Tsirkin wrote: > > On Tue, May 05, 2020 at 04:50:13PM +0200, David Hildenbrand wrote: > >> On 05.05.20 16:15, kbuild test robot wrote: > >>> tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost > >>> head:
2010 Feb 28
3
[PULL] virtio
Linus, Rusty asked me to resolve any issues with virtio and lguest that surface, so here comes. Thanks! The following changes since commit 847f9c606cad121cebf984639e3eeee1c4db82f8: Linus Torvalds (1): Merge branch 'for-linus' of git://git.kernel.org/.../geert/linux-m68k are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
2010 Feb 28
3
[PULL] virtio
Linus, Rusty asked me to resolve any issues with virtio and lguest that surface, so here comes. Thanks! The following changes since commit 847f9c606cad121cebf984639e3eeee1c4db82f8: Linus Torvalds (1): Merge branch 'for-linus' of git://git.kernel.org/.../geert/linux-m68k are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git
2015 Jan 15
2
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, 2015-01-15 at 17:51 +0000, Michael S. Tsirkin wrote: > > > I think you shouldn't use VIRTIO_MMIO_VRING_ALIGN in non-legacy code: > > > it's a legacy thing. > > > > But I still need to pass something to vring_new_virtqueue() below, don't > > I? And it will allocate the queue based on some alignment value. I can't > > see anything
2015 Jan 15
2
[RFC] virtio-mmio: Update the device to OASIS spec version
On Thu, 2015-01-15 at 17:51 +0000, Michael S. Tsirkin wrote: > > > I think you shouldn't use VIRTIO_MMIO_VRING_ALIGN in non-legacy code: > > > it's a legacy thing. > > > > But I still need to pass something to vring_new_virtqueue() below, don't > > I? And it will allocate the queue based on some alignment value. I can't > > see anything
2014 Dec 11
3
[PULL] virtio: virtio 1.0 support, misc patches
The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d: Linux 3.18 (2014-12-07 14:21:05 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 803cd18f7b5e6c7ad6bee9571ae8f4450190ab58: virtio_ccw: finalize_features error handling (2014-12-09 16:32:41 +0200) Note: some
2014 Dec 11
3
[PULL] virtio: virtio 1.0 support, misc patches
The following changes since commit b2776bf7149bddd1f4161f14f79520f17fc1d71d: Linux 3.18 (2014-12-07 14:21:05 -0800) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git tags/for_linus for you to fetch changes up to 803cd18f7b5e6c7ad6bee9571ae8f4450190ab58: virtio_ccw: finalize_features error handling (2014-12-09 16:32:41 +0200) Note: some
2023 May 23
1
vhost stable branch
On Tue, 2023-05-23 at 04:18 -0400, Michael S. Tsirkin wrote: > On Tue, May 23, 2023 at 07:16:58AM +0000, Dragos Tatulea wrote: > > Hi, > > > > I am looking for the stable branch for vdpa fixes in the vhost tree [1]. > > There > > are 3 branches that seem identical: linux-next, test and vhost. linux-next > > seems > > to be -next branch. Which one would