Apparently, not all page faults on the guest result in a page fault in the
host. I would like to intercept page faults on the guest that are not handled
by the host.
I am not quite sure where (in the source code) can I monitor that?
Can any one give me code pointers to look at?
As a test, I removed anywhere my patch stored the size of the shared
memory region and hard coded the size of 512 MB into qemu_ram_alloc
and pci_register_bar, so that my patch never writes the size of the
memory region anywhere. And I discovered that the value of 512MB
still shows up at the
Date: Wed, 3 Mar 2010 15:09:17 -0700
Subject: Re: IVSHMEM and limits on shared memory
From: c...@cs.ualberta.ca
To: kz...@hotmail.com
CC: kvm@vger.kernel.org
On Wed, Mar 3, 2010 at 12:06 AM, Khaled Ibrahim wrote:
Hi Cam,
I used your patches
Hi Cam,
I used your patches successfully to support shared memory on KVM and
used the test cases successfully, but qemu-kvm crashes when I increased the
size of the shared memory. I
applied the ivshmem patch to qemu-kvm-0.12.3 (some manual patching was
needed). It worked flawlessly for
up
Cam,I am interested in the shared memory support you developed on
KVM, but the whole process is not very clear to me. I patched the kernel on the
guest OSs and used the samples codes found in
http://www.mail-archive.com/kvm@vger.kernel.org/msg13328.html, but the
applications fails in mmap.
