From: Muli Ben-Yehuda <mulix@hypervisorconsulting.com>
To: Florian Pester <florian.pester@tu-dresden.de>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: VMCALL to KVM userspace?
Date: Wed, 14 Aug 2013 22:55:49 +0300 [thread overview]
Message-ID: <20130814195549.GE15643@needle> (raw)
In-Reply-To: <520A43CD.1040809@tu-dresden.de>
On Tue, Aug 13, 2013 at 04:33:49PM +0200, Florian Pester wrote:
> for a uni project I'm trying to write a userspace for KVM that can
> run ELF binaries without a full blown OS in the guest. The idea is
> to handle any syscalls made by the binary running inside the guest
> in the userspace of the host. In the simplest case you could forward
> them to the host Linux kernel.
Sounds a lot like Dune,
http://www.scs.stanford.edu/~dm/home/papers/belay:dune.pdf.
> If this is correct, is there any way to make a call to the host VMM,
> that will be transfered to userspace by KVM?
(Paolo already answered)
Cheers,
Muli
prev parent reply other threads:[~2013-08-14 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 14:33 VMCALL to KVM userspace? Florian Pester
2013-08-13 15:43 ` Paolo Bonzini
2013-08-14 19:55 ` Muli Ben-Yehuda [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=20130814195549.GE15643@needle \
--to=mulix@hypervisorconsulting.com \
--cc=florian.pester@tu-dresden.de \
--cc=kvm@vger.kernel.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