lkml.org 
[lkml]   [2012]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v3 6/6] KVM: introduce readonly memslot
On 06/16/2012 10:11 AM, Marcelo Tosatti wrote:

> On Tue, Jun 12, 2012 at 10:49:31AM +0800, Xiao Guangrong wrote:
>> In current code, if we map a readonly memory space from host to guest
>> and the page is not currently mapped in the host, we will get a fault-pfn
>> and async is not allowed, then the vm will crash
>>
>> Address Avi's idea, we introduce readonly memory region to map ROM/ROMD
>> to the guest
>
> Please detail what is the idea in the changelog (a commit message should
> contain information or precise references to discussions).
>


Okay, sorry for my laze.


>> Signed-off-by: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
>> ---
>> Documentation/virtual/kvm/api.txt | 9 ++++--
>> arch/x86/kvm/x86.c | 1 +
>> include/linux/kvm.h | 4 ++-
>> virt/kvm/kvm_main.c | 61 ++++++++++++++++++++++++++++--------
>> 4 files changed, 57 insertions(+), 18 deletions(-)
>>
>> diff --git a/Documentation/virtual/kvm/api.txt b/Documentation/virtual/kvm/api.txt
>> index 310fe50..a97ee90 100644
>> --- a/Documentation/virtual/kvm/api.txt
>> +++ b/Documentation/virtual/kvm/api.txt
>> @@ -857,7 +857,8 @@ struct kvm_userspace_memory_region {
>> };
>>
>> /* for kvm_memory_region::flags */
>> -#define KVM_MEM_LOG_DIRTY_PAGES 1UL
>> +#define KVM_MEM_LOG_DIRTY_PAGES (1UL << 0)
>> +#define KVM_MEM_READONLY (1UL << 1)
>>
>> This ioctl allows the user to create or modify a guest physical memory
>> slot. When changing an existing slot, it may be moved in the guest
>> @@ -873,9 +874,11 @@ It is recommended that the lower 21 bits of guest_phys_addr and userspace_addr
>> be identical. This allows large pages in the guest to be backed by large
>> pages in the host.
>>
>> -The flags field supports just one flag, KVM_MEM_LOG_DIRTY_PAGES, which
>> +The flags field supports two flag, KVM_MEM_LOG_DIRTY_PAGES, which
>> instructs kvm to keep track of writes to memory within the slot. See
>> -the KVM_GET_DIRTY_LOG ioctl.
>> +the KVM_GET_DIRTY_LOG ioctl. Another flag is KVM_MEM_READONLY, which
>> ++indicates the guest memory is read-only, that means, guest is only allowed
>> ++to read it. Writes will be posted to userspace as KVM_EXIT_MMIO exits.
>
> Can you introduce a separate exit reason, say KVM_EXIT_READ_FAULT, with
> information about the fault?
>


KVM_EXIT_READ_FAULT should be KVM_EXIT_WRITE_FAULT :)

The exit info is mostly the same as mmio-exit except this exit does not need
is_write.

> Then perform this exit only if userspace allows it by explicit enable,
> and by default have the exit_read_fault handler jump to the mmio
> handler.
>


No object to do this, but do we need do it in kernel? The userspace can recognise
this fault: if it is a write-mmio-exit and the memslot is readonly.

>> +static bool vma_is_valid(struct vm_area_struct *vma, bool write_fault)
>> +{
>> + if (unlikely(!(vma->vm_flags & VM_READ)))
>> + return false;
>> +
>> + if (write_fault && (unlikely(!(vma->vm_flags & VM_WRITE))))
>> + return false;
>> +
>> + return true;
>> +}
>> +
>> +static int hva_to_pfn_fast(unsigned long addr, bool atomic, bool *async,
>> + bool slot_writable, bool *writable, struct page **page)
>> +{
>> + int npages = 0;
>> +
>> + if (!slot_writable)
>> + return 0;
>> +
>> + if (writable)
>> + *writable = true;
>> +
>> + if (atomic || async)
>> + npages = __get_user_pages_fast(addr, 1, 1, page);
>> +
>> + return npages;
>> +}
>> +
>> static pfn_t hva_to_pfn(struct kvm *kvm, struct kvm_memory_slot *slot,
>> unsigned long addr, bool atomic, bool *async,
>> bool write_fault, bool *writable)
>> @@ -1105,18 +1140,16 @@ static pfn_t hva_to_pfn(struct kvm *kvm, struct kvm_memory_slot *slot,
>> struct page *page[1];
>> int npages = 0;
>> pfn_t pfn;
>> + bool slot_writable = !(slot->flags & KVM_MEM_READONLY);
>>
>> /* we can do it either atomically or asynchronously, not both */
>> BUG_ON(atomic && async);
>>
>> BUG_ON(!write_fault && !writable);
>> + BUG_ON(write_fault && !slot_writable);
>
> Why BUG_ON on this condition?
>


The 'slot' has already been checked in gfn_to_hva_*() functions:

+ if (!slot || slot->flags & KVM_MEMSLOT_INVALID ||
+ ((slot->flags & KVM_MEM_READONLY) && write))
return bad_hva();
So, it is a bug if we get a writable pfn from a readonly slot which
is got from __gfn_to_hva_many(..., write=false).






\
 
 \ /
  Last update: 2012-06-18 06:01    [from the cache]
©2003-2014 Jasper Spaans. Advertise on this site