Hi!
> P.S. Sorry if the question is stupid, i'm not really familiar in hugetlb
> details. I only know
> that managing huge pages is done via hugetlbfs.
Ops, i was double-stupid. :) The question should have actually been: "How to
configure ivshmem to use hugetlb with the series?"
Kind regard
Hi
On Wed, Oct 7, 2015 at 4:22 PM, Pavel Fedin wrote:
> But what will cause memory-backend-ram to use hugetlb instead of just a RAM?
>
> P.S. Sorry if the question is stupid, i'm not really familiar in hugetlb
> details. I only know that managing huge pages is done via hugetlbfs.
Ah right, d
Hello!
> It is like other memdev properties, and there is an example in the
> patch adding a test:
> -object memory-backend-ram,size=1M,id=mb1 -device ivshmem,memdev=mb1
But what will cause memory-backend-ram to use hugetlb instead of just a RAM?
P.S. Sorry if the question is stupid, i'm not
Hi
On Wed, Oct 7, 2015 at 3:50 PM, Pavel Fedin wrote:
> Ok. In this case a single question. How to configure qemu to use ivshmem
> with the series. I have seen that "ivshmem can now use host memory backend",
> but how to set it up? I checked documentation patch, did not find good
> explanatio
Hello!
> The authorship conflict is related to a single commit that could
> easily be dropped in the next pull request. It's worth it if you could
> test before it before it's actually merge!
Ok. In this case a single question. How to configure qemu to use ivshmem with
the series. I have seen
Hi
On Wed, Oct 7, 2015 at 3:13 PM, Pavel Fedin wrote:
> I see there's a PULL, and i was waiting for it to be merged in order to
> test. But, is it going to
> happen? I see there's some strong authorship-related conflict around it.
The authorship conflict is related to a single commit that coul
Hello!
> ivshmem is getting a big reboot right now. See this series
> "[PATCH v5 00/48] ivshmem improvements". Part of that work
> is to better support sharing huge pages.
I see there's a PULL, and i was waiting for it to be merged in order to test.
But, is it going to
happen? I see there's so
On Tue, Oct 06, 2015 at 04:33:23PM +0300, Pavel Fedin wrote:
> This patch permits to share memory areas that do not specifically belong to
> /dev/shm. In such case, the file must be already present when launching qemu.
> A new parameter 'file' has been added to specify the file to use.
>
> A use c
This patch permits to share memory areas that do not specifically belong to
/dev/shm. In such case, the file must be already present when launching qemu.
A new parameter 'file' has been added to specify the file to use.
A use case for this patch is sharing huge pages available through a
hugetlbfs
