From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v5 00/12] KVM: introduce readonly memslot Date: Wed, 15 Aug 2012 13:44:14 +0300 Message-ID: <502B7D7E.20902@redhat.com> References: <5020E423.9080004@linux.vnet.ibm.com> <20120810181422.GA14892@amt.cnet> <502A5A01.6040505@redhat.com> <20120814155106.GA22249@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Xiao Guangrong , LKML , KVM To: Marcelo Tosatti Return-path: In-Reply-To: <20120814155106.GA22249@amt.cnet> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/14/2012 06:51 PM, Marcelo Tosatti wrote: >> >> Userspace may want to modify the ROM (for example, when programming a >> flash device). It is also possible to map an hva range rw through one >> slot and ro through another. > > Right, can do that with multiple userspace maps to the same anonymous > memory region (see other email). Yes it's possible. It requires that we move all memory allocation to be fd based, since userspace can't predict what memory will be dual-mapped (at least if emulated hardware allows this). Is this a reasonable requirement? Do ksm/thp/autonuma work with this? -- error compiling committee.c: too many arguments to function