Hi,
On 06-07-17 11:44, Knut St. Osmundsen wrote:
Hi Hans.
On 2017-07-06 11:13 AM, Hans de Goede wrote:
Hi,
VbglPhysHeapAlloc seems to be yet another mem-allocator
which chunks up memory returned by RTMemContAlloc, which
returns physical contiguous memory below 4GB.
Need for keeping the code
Hello Hans,
06.07.2017 11:44, Knut St. Osmundsen wrote:
> Hi Hans.
>
> On 2017-07-06 11:13 AM, Hans de Goede wrote:
>> Hi,
>>
>> VbglPhysHeapAlloc seems to be yet another mem-allocator
>> which chunks up memory returned by RTMemContAlloc, which
>> returns physical contiguous memory below 4GB.
>
Hi Hans.
On 2017-07-06 11:13 AM, Hans de Goede wrote:
> Hi,
>
> VbglPhysHeapAlloc seems to be yet another mem-allocator
> which chunks up memory returned by RTMemContAlloc, which
> returns physical contiguous memory below 4GB.
Need for keeping the code cross platform, not all supported guest have
Hi,
VbglPhysHeapAlloc seems to be yet another mem-allocator
which chunks up memory returned by RTMemContAlloc, which
returns physical contiguous memory below 4GB.
I don't see any reason why we cannot use kmalloc directly
for that with a GFP_DMA32 flag.
One other thing which RTMemContAlloc
