From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] KVM: Veirfy memory slot only for readability Date: Sun, 04 Dec 2011 19:34:20 +0200 Message-ID: <4EDBAF1C.3050308@redhat.com> References: <1322768576-9242-1-git-send-email-levinsasha928@gmail.com> <4ED826CA.5030502@oss.ntt.co.jp> <4ED84314.5070107@oss.ntt.co.jp> <1322804776.3619.3.camel@lappy> <4EDBA585.2090807@redhat.com> <1323019756.3256.1.camel@lappy> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Takuya Yoshikawa , linux-kernel@vger.kernel.org, Marcelo Tosatti , kvm@vger.kernel.org, Takuya Yoshikawa To: Sasha Levin Return-path: In-Reply-To: <1323019756.3256.1.camel@lappy> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 12/04/2011 07:29 PM, Sasha Levin wrote: > On Sun, 2011-12-04 at 18:53 +0200, Avi Kivity wrote: > > 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. > > Why would I lose hugepage if the kernel gets it's own memory slot? (transparent) hugepages only work on anonymous memory. Hopefully later it will be extended to work on mapped memory as well. -- error compiling committee.c: too many arguments to function