On Thu, Mar 4, 2010 at 1:12 PM, Khaled Ibrahim wrote:
>
>>
>> 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
>
> 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 a
On Wed, Mar 3, 2010 at 3:38 PM, Khaled Ibrahim wrote:
>
>
>
>
>> 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
>> C
> 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:
>&
On Wed, Mar 3, 2010 at 12:06 AM, Khaled Ibrahim wrote:
>
> 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 (
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 to
