Displaying 11 results from an estimated 11 matches for "vq_name".
Did you mean:
vg_name
2020 Apr 28
5
[PATCH 0/1] Add uvirtio for testing
This is a way to create virtio based devices from user space. This is the
background for this patch:
We have some images works fine under qemu, we'd like to also run the same image
on Google Cloud. Currently Google Cloud doesn't support virtio-vga. I had a
patch to create a virtio-vga from kernel directly:
https://www.spinics.net/lists/dri-devel/msg248573.html
Then I got feedback from
2020 Apr 28
5
[PATCH 0/1] Add uvirtio for testing
This is a way to create virtio based devices from user space. This is the
background for this patch:
We have some images works fine under qemu, we'd like to also run the same image
on Google Cloud. Currently Google Cloud doesn't support virtio-vga. I had a
patch to create a virtio-vga from kernel directly:
https://www.spinics.net/lists/dri-devel/msg248573.html
Then I got feedback from
2020 Apr 30
2
[PATCH 0/1] Add uvirtio for testing
On Wed, Apr 29, 2020 at 08:59:18PM -0700, lepton wrote:
> On Wed, Apr 29, 2020 at 4:58 AM Gerd Hoffmann <kraxel at redhat.com> wrote:
> >
> > > 3) Need to be verbose on how the vring processing work in the commit log of
> > > patch 1
> >
> > Ecven better a file documenting the interface somewhere in
> > Documentation/
> I put a uvirtio-vga.c
2009 Jun 23
4
virtio-serial: A guest <-> host interface for simple communication
Hello,
Here are two patches. One implements a virtio-serial device in qemu
and the other is the driver for a guest kernel.
While working on a vmchannel interface that is needed for communication
between guest userspace and host userspace, I saw that most of the
interface can be abstracted out as a "serial" device with "ports".
Some requirements for a vmchannel are listed at
2009 Jun 23
4
virtio-serial: A guest <-> host interface for simple communication
Hello,
Here are two patches. One implements a virtio-serial device in qemu
and the other is the driver for a guest kernel.
While working on a vmchannel interface that is needed for communication
between guest userspace and host userspace, I saw that most of the
interface can be abstracted out as a "serial" device with "ports".
Some requirements for a vmchannel are listed at
2009 Aug 05
0
[PATCH] virtio_serial: A char device for simple guest <-> host communication
...t(virtserconf);
+ if (port_nr == VIRTIO_SERIAL_BAD_ID)
+ continue;
+ ret = virtserial_add_port(port_nr);
+ if (!ret)
+ virtserial.config->nr_active_ports++;
+ }
+ kfree(virtserconf);
+}
+
+static int virtserial_probe(struct virtio_device *vdev)
+{
+ struct virtqueue *vqs[2];
+ const char *vq_names[] = { "input", "output" };
+ vq_callback_t *vq_callbacks[] = { rx_intr, tx_intr };
+ u32 i, map;
+ int ret, map_i;
+ u32 max_nr_ports;
+
+ vdev->config->get(vdev, offsetof(struct virtio_serial_config,
+ max_nr_ports),
+ &max_nr_ports,
+ sizeof(max_nr_port...
2009 Aug 05
0
[PATCH] virtio_serial: A char device for simple guest <-> host communication
...t(virtserconf);
+ if (port_nr == VIRTIO_SERIAL_BAD_ID)
+ continue;
+ ret = virtserial_add_port(port_nr);
+ if (!ret)
+ virtserial.config->nr_active_ports++;
+ }
+ kfree(virtserconf);
+}
+
+static int virtserial_probe(struct virtio_device *vdev)
+{
+ struct virtqueue *vqs[2];
+ const char *vq_names[] = { "input", "output" };
+ vq_callback_t *vq_callbacks[] = { rx_intr, tx_intr };
+ u32 i, map;
+ int ret, map_i;
+ u32 max_nr_ports;
+
+ vdev->config->get(vdev, offsetof(struct virtio_serial_config,
+ max_nr_ports),
+ &max_nr_ports,
+ sizeof(max_nr_port...
2009 Jul 03
1
[RFC PATCH v3] virito-serial: A guest <-> host interface
Hello,
This is a new iteration of the patches that implement virtio-serial. Changes
include:
* Adding support for port hot-add
* Creating ports at specific ids that can be bound to specific apps / usage
* Cleanups
This code still doesn't get rid of the support for assigning names
to ports but it just has to be ripped out.
Comments welcome.
Thanks,
Amit.
2009 Jul 03
1
[RFC PATCH v3] virito-serial: A guest <-> host interface
Hello,
This is a new iteration of the patches that implement virtio-serial. Changes
include:
* Adding support for port hot-add
* Creating ports at specific ids that can be bound to specific apps / usage
* Cleanups
This code still doesn't get rid of the support for assigning names
to ports but it just has to be ripped out.
Comments welcome.
Thanks,
Amit.
2009 Jul 27
3
virtio-serial: An interface for host-guest communication
Hello all,
This are the latest version of the patches.
Lots of things have changed since the last submission. A few of
which I remember:
- VNC copy / paste works* (* conditions apply)
- client vnc copies get propagated to guest port 3 (/dev/vmch3)
- guest writes to port 3 (/dev/vmch3) go straight to client's clipboard
- sysfs hooks to autodiscover ports
- support for 64 ports in this
2009 Jul 27
3
virtio-serial: An interface for host-guest communication
Hello all,
This are the latest version of the patches.
Lots of things have changed since the last submission. A few of
which I remember:
- VNC copy / paste works* (* conditions apply)
- client vnc copies get propagated to guest port 3 (/dev/vmch3)
- guest writes to port 3 (/dev/vmch3) go straight to client's clipboard
- sysfs hooks to autodiscover ports
- support for 64 ports in this