From: Jan Kiszka <jan.kiszka@siemens.com>
To: kvm <kvm@vger.kernel.org>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics?
Date: Thu, 19 Jan 2012 13:46:39 +0100 [thread overview]
Message-ID: <4F1810AF.8010002@siemens.com> (raw)
Hi again,
do we need some KVM knob comparable to qemu-kvm's -kvm-shadow-memory in
upstream?
If yes: The underlying IOCTL is x86-only. Are other archs interested in
this long-term as well, ie. should the control become arch-independent?
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next reply other threads:[~2012-01-19 12:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 12:46 Jan Kiszka [this message]
2012-01-19 13:24 ` [Qemu-devel] qemu-kvm upstreaming: Do we want -kvm-shadow-memory semantics? Alexander Graf
2012-01-19 13:30 ` Jan Kiszka
2012-01-19 13:42 ` Alexander Graf
2012-01-19 17:28 ` Marcelo Tosatti
2012-01-19 17:39 ` Jan Kiszka
2012-01-25 11:38 ` Avi Kivity
2012-01-25 11:57 ` Jan Kiszka
2012-01-25 12:04 ` Avi Kivity
2012-01-25 12:10 ` Jan Kiszka
2012-01-25 12:15 ` Avi Kivity
2012-01-25 12:26 ` Jan Kiszka
2012-01-25 12:33 ` 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=4F1810AF.8010002@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--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).