From: Anthony Liguori <anthony@codemonkey.ws>
To: "Lluís Vilanova" <vilanova@ac.upc.edu>
Cc: Zhi Yong Wu <zwu.kernel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH 0/5] backdoor: lightweight guest-to-QEMU backdoor channel
Date: Thu, 29 Sep 2011 08:52:52 -0500 [thread overview]
Message-ID: <4E847834.7070805@codemonkey.ws> (raw)
In-Reply-To: <20110929134727.19559.54734.stgit@ginnungagap.bsc.es>
On 09/29/2011 08:47 AM, Lluís Vilanova wrote:
> Provides the ability for the guest to communicate with user-provided code inside
> QEMU itself, using a lightweight mechanism.
>
> See first commit for a full description.
>
> Signed-off-by: Lluís Vilanova<vilanova@ac.upc.edu>
We already have two "backdoors" in QEMU: ivshmem and virtio-serial. Can you
discuss why these are insufficient for your purposes?
Also, what's the advantage of having a backdoor mechanism both for softmmu and
user? I can't think of a practical use-case for it.
Regards,
Anthony Liguori
> ---
>
> Lluís Vilanova (5):
> backdoor: Add documentation
> backdoor: Add build infrastructure
> backdoor: [*-user] Add QEMU-side proxy to "libbackdoor.a"
> backdoor: [softmmu] Add QEMU-side proxy to "libbackdoor.a"
> backdoor: Add guest-side library
>
>
> Makefile | 3 -
> Makefile.objs | 21 ++++
> Makefile.target | 4 +
> backdoor/guest/Makefile | 18 ++++
> backdoor/guest/common.c | 130 +++++++++++++++++++++++++++
> backdoor/guest/qemu-backdoor.h | 50 ++++++++++
> backdoor/qemu/qemu-backdoor.h | 29 ++++++
> backdoor/qemu/softmmu.c | 124 ++++++++++++++++++++++++++
> backdoor/qemu/user.c | 194 ++++++++++++++++++++++++++++++++++++++++
> backdoor/qemu/user.h | 17 ++++
> bsd-user/main.c | 25 +++++
> bsd-user/mmap.c | 7 +
> configure | 35 +++++++
> darwin-user/main.c | 25 +++++
> darwin-user/mmap.c | 7 +
> docs/backdoor.txt | 144 ++++++++++++++++++++++++++++++
> hw/pci.h | 1
> linux-user/main.c | 30 ++++++
> linux-user/mmap.c | 7 +
> 19 files changed, 869 insertions(+), 2 deletions(-)
> create mode 100644 backdoor/guest/Makefile
> create mode 100644 backdoor/guest/common.c
> create mode 100644 backdoor/guest/qemu-backdoor.h
> create mode 100644 backdoor/qemu/qemu-backdoor.h
> create mode 100644 backdoor/qemu/softmmu.c
> create mode 100644 backdoor/qemu/user.c
> create mode 100644 backdoor/qemu/user.h
> create mode 100644 docs/backdoor.txt
>
>
next prev parent reply other threads:[~2011-09-29 13:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-29 13:47 [Qemu-devel] [RFC][PATCH 0/5] backdoor: lightweight guest-to-QEMU backdoor channel Lluís Vilanova
2011-09-29 13:47 ` [Qemu-devel] [PATCH 1/5] backdoor: Add documentation Lluís Vilanova
2011-09-29 13:47 ` [Qemu-devel] [PATCH 2/5] backdoor: Add build infrastructure Lluís Vilanova
2011-09-29 13:47 ` [Qemu-devel] [PATCH 3/5] backdoor: [*-user] Add QEMU-side proxy to "libbackdoor.a" Lluís Vilanova
2011-09-29 13:47 ` [Qemu-devel] [PATCH 4/5] backdoor: [softmmu] " Lluís Vilanova
2011-09-29 20:42 ` Blue Swirl
2011-09-29 21:49 ` Lluís Vilanova
2011-09-29 22:13 ` Frans de Boer
2011-09-29 22:35 ` Frans de Boer
2011-09-30 20:29 ` Blue Swirl
2011-09-30 20:07 ` Blue Swirl
2011-09-30 20:49 ` Lluís Vilanova
2011-09-30 20:59 ` Blue Swirl
2011-09-29 13:47 ` [Qemu-devel] [PATCH 5/5] backdoor: Add guest-side library Lluís Vilanova
2011-09-29 13:52 ` Anthony Liguori [this message]
2011-09-29 17:10 ` [Qemu-devel] [RFC][PATCH 0/5] backdoor: lightweight guest-to-QEMU backdoor channel Lluís Vilanova
2011-09-29 20:55 ` Blue Swirl
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=4E847834.7070805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
--cc=vilanova@ac.upc.edu \
--cc=zwu.kernel@gmail.com \
/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).