From: "Alex Bennée" <alex.bennee@linaro.org>
To: Amit Kumar <amit251098@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Beginner-Help] Help understanding the migration Code
Date: Tue, 17 Oct 2023 18:19:51 +0100 [thread overview]
Message-ID: <875y35b1xb.fsf@linaro.org> (raw)
In-Reply-To: <CAHhcV89tKJiFz6CW5Xm6XP5pDs1uLBew=kjC5qd-k+fNVmdt1g@mail.gmail.com>
Amit Kumar <amit251098@gmail.com> writes:
> Following up on the previous email I sent. I want to understand the migration code, I have read a couple of papers on
> how it works in theory, but I am finding it hard to find a starting
> point where I can start to understand the code.
Start looking at the VMStateDescription and what follows from there.
This is the principle source of serialisation information when saving
and restoring device state.
The VMSTATE_* macros wrap up a lot of the structures.
>
> Any help would be appreciated.
>
> Thank you
>
> On Wed, Oct 11, 2023 at 9:40 AM Amit Kumar <amit251098@gmail.com> wrote:
>
> Hi
> I am trying to understand how migration, more specifically live-migration works in QEMU. I've tried going
> through the source code but didn't understand much, and couldn't find documentation either. I want to work on
> live migration and need help getting to know the code.
> More specifically I want to understand
> - where the pre/post copy algorithms are implemented
> - which files/data-structures that I should look at
> - should I need to make changes, where and how should I start?
>
> I am new to working with such large code bases, hence need some guidance.
>
> Thanks
>
> Amit Kumar
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-10-17 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 4:10 [Beginner-Help] Help understanding the migration Code Amit Kumar
2023-10-17 16:32 ` Amit Kumar
2023-10-17 17:19 ` Alex Bennée [this message]
2023-10-28 8:47 ` Amit Kumar
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=875y35b1xb.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=amit251098@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).