[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH 2/2] hyperv/synic: Allocate as ram_device

From: Vitaly Kuznetsov
Subject: Re: [PATCH 2/2] hyperv/synic: Allocate as ram_device
Date: Thu, 09 Jan 2020 16:40:26 +0100

Paolo Bonzini <address@hidden> writes:

> On 09/01/20 14:22, Dr. David Alan Gilbert wrote:
>> * Michael S. Tsirkin (address@hidden) wrote:
>>> On Thu, Jan 09, 2020 at 12:22:37PM +0000, Dr. David Alan Gilbert wrote:
>>>> Do we want a new memory_region_init for that or just to be able to add
>>>> a flag?
>>> I think a flag API is preferable since this can apply to any kind of
>>> region. But can go either way, Paolo's the maintainer there.
>> (Copying Paolo in)
>> So what exactly does this flag mean; to me it's 'no vhost' - but is it
>> actually more general?
> It has two more effects in addition to no vhost:
> 1) it is skipped when dumping the guest (is this a good or bad idea for
> SynIC?)

Imagine we have an not yet consumed message sitting in message page, or
a signalled event, do I understand correctly that these are going to get
lost upon migration? This may not work then -- unless we transfer
in-QEMU synic state somehow separately.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]