Christian Borntraeger wrote:
> On Thursday 12 April 2007 17:38, Avi Kivity wrote:
>
>>> But wouldn't it also be possible to create a file in
>>> userspace and pass its descriptor to kvm?
>>>
> [...]
>
>> swap, hugetlbfs, and maybe other nifty stuff. I think I know how to do
>> this f
On Thursday 12 April 2007 17:38, Avi Kivity wrote:
> > But wouldn't it also be possible to create a file in
> > userspace and pass its descriptor to kvm?
[...]
> swap, hugetlbfs, and maybe other nifty stuff. I think I know how to do
> this for the current mmu, but I'm worried that it will have a
Laurent Vivier wrote:
> Avi Kivity wrote:
>
>> Michael Riepe wrote:
>>
>>> Hi!
>>>
>>> This is just a (probably silly) idea I had the other day. Currently, the
>>> guest's memory is allocated inside the kernel and exported to userspace
>>> via mmap(). But wouldn't it also be possible to cre
Avi Kivity wrote:
> Michael Riepe wrote:
>> Hi!
>>
>> This is just a (probably silly) idea I had the other day. Currently, the
>> guest's memory is allocated inside the kernel and exported to userspace
>> via mmap(). But wouldn't it also be possible to create a file in
>> userspace and pass its des
Michael Riepe wrote:
> Hi!
>
> This is just a (probably silly) idea I had the other day. Currently, the
> guest's memory is allocated inside the kernel and exported to userspace
> via mmap(). But wouldn't it also be possible to create a file in
> userspace and pass its descriptor to kvm? If we also
Hi!
This is just a (probably silly) idea I had the other day. Currently, the
guest's memory is allocated inside the kernel and exported to userspace
via mmap(). But wouldn't it also be possible to create a file in
userspace and pass its descriptor to kvm? If we also pass file offset
and length par
