qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: fu lirong <best19912228@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] The communication between QEMU and KVM
Date: Mon, 22 Jun 2015 11:09:17 +0100	[thread overview]
Message-ID: <20150622100917.GE20966@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAG=NdOxbyWDYDOiqjA_YaO7Of_XuPtY_T2vJncCD+ngpQvoGUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 359 bytes --]

On Sat, Jun 20, 2015 at 10:53:57PM +0800, fu lirong wrote:
>                   I am wondering  How Qemu communicate  with KVM , for
> example I want to deliver some information in KVM  to Qemu, what should I
> do ?

The kvm.ko userspace API is defined in linux.git
Documentation/virtual/kvm/api.txt, although it depends on what exactly
you are doing.

Stefan

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

      reply	other threads:[~2015-06-22 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20 14:53 [Qemu-devel] The communication between QEMU and KVM fu lirong
2015-06-22 10:09 ` 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=20150622100917.GE20966@stefanha-thinkpad.redhat.com \
    --to=stefanha@gmail.com \
    --cc=best19912228@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).