* [Qemu-devel] Virtio_PCI device driver code
@ 2012-03-14 13:38 Abhinav Pundir
2012-03-14 18:20 ` Brian Jackson
2012-03-15 11:25 ` Stefan Hajnoczi
0 siblings, 2 replies; 3+ messages in thread
From: Abhinav Pundir @ 2012-03-14 13:38 UTC (permalink / raw)
To: qemu-devel
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hello all I am very much new to the world of KVM and Qemu.
I am trying to make a communication possible between the Guest and the Host.
I have studied how Virtio works but I am still confused how exactly the
flow will work.
The front end drivers will communicate to the back end driver by invoking a
kick function, but which back end driver will be involved in that.
Also how the back end driver present in the Hypervisor will pass this
information to the emulated device running in Qemu.
I am trying to use virtio_pci.c and some suitable modification, so that the
back end driver can take that information and that information will
be available to the Hypervisor.
It will be very useful if somebody can provide me the working code of the
virtio_pci with all the dependencies in the separate directory, so that I
will be able to insert that module and the equivalent back-end driver code
running in the Hypervisor.
[-- Attachment #2: Type: text/html, Size: 960 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Virtio_PCI device driver code
2012-03-14 13:38 [Qemu-devel] Virtio_PCI device driver code Abhinav Pundir
@ 2012-03-14 18:20 ` Brian Jackson
2012-03-15 11:25 ` Stefan Hajnoczi
1 sibling, 0 replies; 3+ messages in thread
From: Brian Jackson @ 2012-03-14 18:20 UTC (permalink / raw)
To: qemu-devel, Abhinav Pundir
On Wed, 14 Mar 2012 08:38:04 -0500, Abhinav Pundir
<abhinavmasters@gmail.com> wrote:
> Hello all I am very much new to the world of KVM and Qemu.
> I am trying to make a communication possible between the Guest and the
> Host.
If you just need to communicate, why not just use virtio-serial
functionality?
> I have studied how Virtio works but I am still confused how exactly the
> flow will work.
> The front end drivers will communicate to the back end driver by
> invoking a
> kick function, but which back end driver will be involved in that.
> Also how the back end driver present in the Hypervisor will pass this
> information to the emulated device running in Qemu.
> I am trying to use virtio_pci.c and some suitable modification, so that
> the
> back end driver can take that information and that information will
> be available to the Hypervisor.
>
> It will be very useful if somebody can provide me the working code of the
> virtio_pci with all the dependencies in the separate directory, so that I
> will be able to insert that module and the equivalent back-end driver
> code
> running in the Hypervisor.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Qemu-devel] Virtio_PCI device driver code
2012-03-14 13:38 [Qemu-devel] Virtio_PCI device driver code Abhinav Pundir
2012-03-14 18:20 ` Brian Jackson
@ 2012-03-15 11:25 ` Stefan Hajnoczi
1 sibling, 0 replies; 3+ messages in thread
From: Stefan Hajnoczi @ 2012-03-15 11:25 UTC (permalink / raw)
To: Abhinav Pundir; +Cc: qemu-devel
On Wed, Mar 14, 2012 at 1:38 PM, Abhinav Pundir
<abhinavmasters@gmail.com> wrote:
> Hello all I am very much new to the world of KVM and Qemu.
> I am trying to make a communication possible between the Guest and the Host.
> I have studied how Virtio works but I am still confused how exactly the flow
> will work.
> The front end drivers will communicate to the back end driver by invoking a
> kick function, but which back end driver will be involved in that.
> Also how the back end driver present in the Hypervisor will pass this
> information to the emulated device running in Qemu.
> I am trying to use virtio_pci.c and some suitable modification, so that the
> back end driver can take that information and that information will
> be available to the Hypervisor.
>
> It will be very useful if somebody can provide me the working code of the
> virtio_pci with all the dependencies in the separate directory, so that I
> will be able to insert that module and the equivalent back-end driver code
> running in the Hypervisor.
Please explain what you are trying to achieve. Coding a custom virtio
device may not be the best solution - it depends on the specific use
case.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-03-15 11:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-03-14 13:38 [Qemu-devel] Virtio_PCI device driver code Abhinav Pundir
2012-03-14 18:20 ` Brian Jackson
2012-03-15 11:25 ` Stefan Hajnoczi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).