qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Abhinav Pundir <abhinavmasters@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Virtio_PCI device driver code
Date: Thu, 15 Mar 2012 11:25:46 +0000	[thread overview]
Message-ID: <CAJSP0QWedmNZqb+LLhH3pGs47LNouymh-pomFkvzYh2bOqxoOQ@mail.gmail.com> (raw)
In-Reply-To: <CAGvMnefZwJ=-Fuug7sUvjGKcYwBjkZfEdeScE_O_r6gPJL6EeQ@mail.gmail.com>

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

      parent reply	other threads:[~2012-03-15 11:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAJSP0QWedmNZqb+LLhH3pGs47LNouymh-pomFkvzYh2bOqxoOQ@mail.gmail.com \
    --to=stefanha@gmail.com \
    --cc=abhinavmasters@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).