[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] exclude hyperv synic sections from vhost
|
From: |
Vitaly Kuznetsov |
|
Subject: |
Re: [PATCH 0/2] exclude hyperv synic sections from vhost |
|
Date: |
Thu, 09 Jan 2020 10:07:50 +0100 |
Jason Wang <address@hidden> writes:
> On 2020/1/8 下午9:53, Dr. David Alan Gilbert (git) wrote:
>> From: "Dr. David Alan Gilbert" <address@hidden>
>>
>> Hyperv's synic (that we emulate) is a feature that allows the guest
>> to place some magic (4k) pages of RAM anywhere it likes in GPA.
>> This confuses vhost's RAM section merging when these pages
>> land over the top of hugepages.
>
>
> Hi David:
>
> A silly question, is this because the alignment when adding sections? If
> yes, what's the reason for doing alignment which is not a must for vhost
> memory table.
SynIC regions are two 4k pages and they are picked by the guest, not the
host. These can be anywhere in guest's ram.
--
Vitaly
Re: [PATCH 2/2] hyperv/synic: Allocate as ram_device, Roman Kagan, 2020/01/09
Re: [PATCH 0/2] exclude hyperv synic sections from vhost, Vitaly Kuznetsov, 2020/01/08
Re: [PATCH 0/2] exclude hyperv synic sections from vhost, Jason Wang, 2020/01/08
Re: [PATCH 0/2] exclude hyperv synic sections from vhost, Roman Kagan, 2020/01/09