From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>
Cc: Roman Kagan <rkagan@virtuozzo.com>,
jasowang@redhat.com, "Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [PATCH 2/2] hyperv/synic: Allocate as ram_device
Date: Tue, 7 Jul 2020 12:54:31 +0200 [thread overview]
Message-ID: <57b450ab-313d-5582-0ba9-43c1de0c9e75@redhat.com> (raw)
In-Reply-To: <87h814r639.fsf@vitty.brq.redhat.com>
On 09/01/20 16:40, Vitaly Kuznetsov 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.
(Thread necromancy).
This is just dumping (and it should probably be extended to core
dumping, i.e. MADV_DONTDUMP). Migration is controlled separately with
vmstate_register_ram.
Paolo
next prev parent reply other threads:[~2020-07-07 10:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 13:53 [PATCH 0/2] exclude hyperv synic sections from vhost Dr. David Alan Gilbert (git)
2020-01-08 13:53 ` [PATCH 1/2] vhost: Don't pass ram device sections Dr. David Alan Gilbert (git)
2020-01-09 11:45 ` Michael S. Tsirkin
2020-01-09 11:56 ` Michael S. Tsirkin
2020-01-09 12:38 ` Roman Kagan
2020-01-09 12:42 ` Michael S. Tsirkin
2020-01-08 13:53 ` [PATCH 2/2] hyperv/synic: Allocate as ram_device Dr. David Alan Gilbert (git)
2020-01-09 11:48 ` Michael S. Tsirkin
2020-01-09 12:08 ` Dr. David Alan Gilbert
2020-01-09 12:18 ` Michael S. Tsirkin
2020-01-09 12:22 ` Dr. David Alan Gilbert
2020-01-09 13:00 ` Vitaly Kuznetsov
2020-01-09 13:24 ` Roman Kagan
2020-01-09 13:28 ` Dr. David Alan Gilbert
2020-01-09 16:12 ` Roman Kagan
2020-01-09 16:27 ` Dr. David Alan Gilbert
2020-01-09 17:13 ` Roman Kagan
2020-01-09 13:06 ` Michael S. Tsirkin
2020-01-09 13:22 ` Dr. David Alan Gilbert
2020-01-09 13:27 ` Michael S. Tsirkin
2020-01-09 13:28 ` Michael S. Tsirkin
2020-01-09 13:40 ` Dr. David Alan Gilbert
2020-01-09 15:31 ` Paolo Bonzini
2020-01-09 15:38 ` Dr. David Alan Gilbert
2020-01-09 15:40 ` Vitaly Kuznetsov
2020-07-07 10:54 ` Paolo Bonzini [this message]
2020-01-09 13:03 ` Roman Kagan
2020-01-09 13:08 ` Dr. David Alan Gilbert
2020-01-08 14:26 ` [PATCH 0/2] exclude hyperv synic sections from vhost Vitaly Kuznetsov
2020-01-09 3:00 ` Jason Wang
2020-01-09 9:07 ` Vitaly Kuznetsov
2020-01-09 12:02 ` Dr. David Alan Gilbert
2020-01-09 12:14 ` Michael S. Tsirkin
2020-01-09 11:53 ` Roman Kagan
2020-01-09 12:16 ` Dr. David Alan Gilbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57b450ab-313d-5582-0ba9-43c1de0c9e75@redhat.com \
--to=pbonzini@redhat.com \
--cc=dgilbert@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=vkuznets@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).