On 13/01/20 18:36, Dr. David Alan Gilbert (git) wrote: > > 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.
Can you explain what is the confusion like? The memory API should just tell vhost to treat it as three sections (RAM before synIC, synIC region, RAM after synIC) and it's not clear to me why postcopy breaks either. Paolo > Since they're not normal RAM, and they shouldn't have vhost DMAing > into them, exclude them from the vhost set.
