lkml.org 
[lkml]   [2012]   [Aug]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v5 00/12] KVM: introduce readonly memslot
On 08/16/2012 06:57 PM, Marcelo Tosatti wrote:
>>
>> Correct. But the chipset is also able to to write-protect some ranges
>> in the 0xc0000-0x100000 area via the PAM. It is able to write-protect
>> both RAM and PCI memory (usually mapped to flash).
>
> You are convinced that adding read-write protection information to the
> memory slots, which controls access by the guest, in addition to the
> userspace host pagetables, is useful. OK.

In fact if we started from scratch I'd go for one huge slot, with
PROT_NONE for mmio and non-kvm APIs for dirty bitmaps, and use Linux mm
APIs to manage the details. This would make kvm x86_64 only (no way to
access the PCI space on i386) but it would simplify a lot of the
internal translation layer. But we're not there.


--
error compiling committee.c: too many arguments to function


\
 
 \ /
  Last update: 2012-08-17 02:21    [W:0.076 / U:0.244 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site