From: Amit Kumar <amit251098@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Beginner-Help] Help understanding the migration Code
Date: Wed, 11 Oct 2023 09:40:09 +0530 [thread overview]
Message-ID: <CAHhcV8-HHG36Ndv7Y-K5FrUTb-WwVoRW3PPzaiM4hEesGA-iWw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 576 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 753 bytes --]
next reply other threads:[~2023-10-11 4:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-11 4:10 Amit Kumar [this message]
2023-10-17 16:32 ` [Beginner-Help] Help understanding the migration Code Amit Kumar
2023-10-17 17:19 ` Alex Bennée
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=CAHhcV8-HHG36Ndv7Y-K5FrUTb-WwVoRW3PPzaiM4hEesGA-iWw@mail.gmail.com \
--to=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).