From: Arn <cse.syslab@gmail.com>
To: "Avi Kivity" <avi@qumranet.com>
Cc: kvm@vger.kernel.org
Subject: Re: Sharing variables/memory between host and guest ?
Date: Mon, 14 Jul 2008 17:43:04 -0400 [thread overview]
Message-ID: <896ae46a0807141443p78df612csb5801d8ae7af17ca@mail.gmail.com> (raw)
In-Reply-To: <4879D494.7020803@qumranet.com>
>> How can one share memory (a few variables not necessarily a page)
>> between host/hypervisor and guest VM ?
>>
> If you use the -mem-path qemu option, all guest memory will be in a file on
> tmpfs. You can mmap that file and access all guest memory. Of course, this
> is hitting the problem with a fairly bit hammer; more refined approaches are
> possible.
Could you outline the other approaches ?
Thanks
arn
next prev parent reply other threads:[~2008-07-14 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 0:16 Sharing variables/memory between host and guest ? Arn
2008-07-12 12:33 ` Dor Laor
2008-07-12 21:03 ` Arn
2008-07-12 21:15 ` Eric Van Hensbergen
2008-07-12 21:59 ` Arn
2008-07-12 22:06 ` Eric Van Hensbergen
2008-07-13 10:10 ` Avi Kivity
2008-07-14 21:43 ` Arn [this message]
2008-07-19 8:29 ` Avi Kivity
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=896ae46a0807141443p78df612csb5801d8ae7af17ca@mail.gmail.com \
--to=cse.syslab@gmail.com \
--cc=avi@qumranet.com \
--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