search for: ram_huge

...4:09 AM, David Hildenbrand <david at redhat.com> wrote: > Btw, I am thinking about the following addition to the concept: > > 1. Add a type to each virtio-mem device. > > This describes the type of the memory region we expose to the guest. > Initially, we could have RAM and RAM_HUGE. The latter one would be > interesting, because the guest would know that this memory is based on > huge pages in case we would ever want to expose different RAM types to a > guest (the guest could conclude that this memory might be faster and > would also best be used with huge pages i...

...4:09 AM, David Hildenbrand <david at redhat.com> wrote: > Btw, I am thinking about the following addition to the concept: > > 1. Add a type to each virtio-mem device. > > This describes the type of the memory region we expose to the guest. > Initially, we could have RAM and RAM_HUGE. The latter one would be > interesting, because the guest would know that this memory is based on > huge pages in case we would ever want to expose different RAM types to a > guest (the guest could conclude that this memory might be faster and > would also best be used with huge pages i...

...and <david at redhat.com> wrote: >> Btw, I am thinking about the following addition to the concept: >> >> 1. Add a type to each virtio-mem device. >> >> This describes the type of the memory region we expose to the guest. >> Initially, we could have RAM and RAM_HUGE. The latter one would be >> interesting, because the guest would know that this memory is based on >> huge pages in case we would ever want to expose different RAM types to a >> guest (the guest could conclude that this memory might be faster and >> would also best be used w...

Btw, I am thinking about the following addition to the concept: 1. Add a type to each virtio-mem device. This describes the type of the memory region we expose to the guest. Initially, we could have RAM and RAM_HUGE. The latter one would be interesting, because the guest would know that this memory is based on huge pages in case we would ever want to expose different RAM types to a guest (the guest could conclude that this memory might be faster and would also best be used with huge pages in the guest). But we...

Hi, this is an idea that is based on Andrea Arcangeli's original idea to host enforce guest access to memory given up using virtio-balloon using userfaultfd in the hypervisor. While looking into the details, I realized that host-enforcing virtio-balloon would result in way too many problems (mainly backwards compatibility) and would also have some conceptual restrictions that I want to avoid.

Hi, this is an idea that is based on Andrea Arcangeli's original idea to host enforce guest access to memory given up using virtio-balloon using userfaultfd in the hypervisor. While looking into the details, I realized that host-enforcing virtio-balloon would result in way too many problems (mainly backwards compatibility) and would also have some conceptual restrictions that I want to avoid.