From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
linux-kernel@vger.kernel.org,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org,
Takuya Yoshikawa <takuya.yoshikawa@gmail.com>
Subject: Re: [PATCH] KVM: Veirfy memory slot only for readability
Date: Sun, 04 Dec 2011 18:53:25 +0200 [thread overview]
Message-ID: <4EDBA585.2090807@redhat.com> (raw)
In-Reply-To: <1322804776.3619.3.camel@lappy>
On 12/02/2011 07:46 AM, Sasha Levin wrote:
> > Do you want to create read only memory slots for kvm tool?
>
> What KVM tool currently does is copy the kernel into guest memory and
> run it from there. An idea raised recently was instead of copying it we
> should mmap it into the memory to reduce footprint.
>
> This is why I'm looking into adding a read only memory slot. The KVM
> code doesn't have to know it's read only.
The kernel will patch itself very early. You need to use MAP_PRIVATE
(and thus have a read/write area). It will be interesting to see what
fraction of the memory is modified.
Note that mapping will remove benefits like huge page support, and that
you can get page sharing by using ksm. Still, it's interesting to see
where this goes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-12-04 16:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 19:42 [PATCH] KVM: Veirfy memory slot only for readability Sasha Levin
2011-12-02 1:15 ` Takuya Yoshikawa
2011-12-02 3:16 ` Takuya Yoshikawa
2011-12-02 5:46 ` Sasha Levin
2011-12-02 6:39 ` Takuya Yoshikawa
2011-12-04 16:53 ` Avi Kivity [this message]
2011-12-04 17:29 ` Sasha Levin
2011-12-04 17:34 ` Avi Kivity
2011-12-04 19:10 ` Sasha Levin
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=4EDBA585.2090807@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=takuya.yoshikawa@gmail.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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