From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Anton Kuchin <antonkuchin@yandex-team.ru>, marcandre.lureau@redhat.com
Cc: qemu-devel@nongnu.org, yc-core@yandex-team.ru, mst@redhat.com
Subject: Re: vhost-user: questions regarding migration
Date: Tue, 22 Sep 2020 20:07:22 +0100 [thread overview]
Message-ID: <20200922190722.GD2837@work-vm> (raw)
In-Reply-To: <6ef03e9e-aaff-ce20-7f61-0771fcf007eb@yandex-team.ru>
* Anton Kuchin (antonkuchin@yandex-team.ru) wrote:
> Hi,
>
> I'm implementing migration support in vhost-user backend and have a
> couple of questions:
Hi Anton,
I'ts a while since I've looked at this code, but from memory:
> 1. How master can be sure that logging was started?
>
> We expect that right after set_fatures command with VHOST_F_LOG_ALL flag
> all memory modifications will be tracked in log, but slave can need a
> little time to process this command so there is a chance that some
> requests can be untracked. Is there a way to ensure all requests are
> logged or determine the moment since when tracking starts and master can
> start migrating memory?
I think it happens after the set_mem_table command; I think if the
command had the 'NEED_REPLY' flag set then the client responds to the
qemu to say the command is done.
> 2. Why do we need separate log_addr for vring and how can it be not
> covered by mem table?
Hmm I don't think I understand that question; isn't the vring covered by
the memtable?
> As far as I understand slave receives used address in set_vring_addr
> command and to map it correctly we do need valid entry in memory table.
> So this field looks redundant to me. Am I missing something?
>
> BTW the word "log_guest_addr" is mentioned only once in the document and
> in "vring address description" payload it is just called "log",
> shouldn't we should change this names to match?
Let's cc in Marc-Andre.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
prev parent reply other threads:[~2020-09-22 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 2:59 vhost-user: questions regarding migration Anton Kuchin
2020-09-22 19:07 ` Dr. David Alan Gilbert [this message]
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=20200922190722.GD2837@work-vm \
--to=dgilbert@redhat.com \
--cc=antonkuchin@yandex-team.ru \
--cc=marcandre.lureau@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yc-core@yandex-team.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.