Hi, KVM developer:
A correction to my previous post. I found that NOT all page fault in
the guest could cause kvm_page_fault event in the hypervisor.
For example, my array access microbencharmk touches 1024 pages (as an
integer array). In the guest VM, I can trace 1024 page fault events.
However,
Hi, Paolo,
As you said the memory pages may have already be touched by the guest,
although it still cause page fault from the VM.
So my question is will KVM pre-allocate some physical pages (by
calling get_user_page_fast) to the guest?
If so, when a user-space program in the guest requests for pag
On Thu, Sep 18, 2014 at 6:00 AM, Paolo Bonzini wrote:
> Il 18/09/2014 01:11, Steven ha scritto:
>> I agree with you that the memory allocated from the
>> kmem_cache_alloc_node and kmalloc_node should be not returned to the
>> user space process in the VM.
>>
>> Can I understand in this way " for s
Il 17/09/2014 05:56, Steven ha scritto:
> When size = 10MB and 20MB, it looks like that KVM use
> kmem_cache_alloc_node and kmalloc_node to allocate physical pages.
> However, when size = 40MB, KVM hypervisor uses mm_page_alloc to
> allocator physical pages. The former is based on the slab allocato
Dear KVM Developers:
I have some questions about how KVM hypervisor requests and allocate
physical pages to the VM. I am using kernel version 3.2.14.
I run a microbenchmark in the VM, which declares an array with certain
size and then assigns some value to all the elements in the array,
which caus
