search for: free_invqs

Displaying 4 results from an estimated 4 matches for "free_invqs".

Did you mean: free_in_vq
2010 May 18
1
[PATCH] fix a code style in drivers/char/virtio_console.c
...gt;in_vqs) { - err = -ENOMEM; goto free_names; } portdev->out_vqs = kmalloc(nr_ports * sizeof(struct virtqueue *), GFP_KERNEL); if (!portdev->out_vqs) { - err = -ENOMEM; goto free_invqs; } -- 1.7.1 Best regards
2010 May 18
1
[PATCH] fix a code style in drivers/char/virtio_console.c
...gt;in_vqs) { - err = -ENOMEM; goto free_names; } portdev->out_vqs = kmalloc(nr_ports * sizeof(struct virtqueue *), GFP_KERNEL); if (!portdev->out_vqs) { - err = -ENOMEM; goto free_invqs; } -- 1.7.1 Best regards
2010 Jan 29
3
virtio: console: Return -EFAULT on copy_xx_user errors, allow larger writes
Hey Rusty, These updated patches in the series return -EFAULT on copy_xx_user errors and also move the copy_from_user into fops_write() instead of it being in send_buf. This enables send_buf to just read from kernel buffers, making it simpler. This also allows write()s to write more to the host in one go, removingthe 4k limitation. I do limit the writes to 32k at once to not put too much
2010 Jan 29
3
virtio: console: Return -EFAULT on copy_xx_user errors, allow larger writes
Hey Rusty, These updated patches in the series return -EFAULT on copy_xx_user errors and also move the copy_from_user into fops_write() instead of it being in send_buf. This enables send_buf to just read from kernel buffers, making it simpler. This also allows write()s to write more to the host in one go, removingthe 4k limitation. I do limit the writes to 32k at once to not put too much