From: Manoj Yadav <mkycse@gmail.com>
To: xen-devel@lists.xen.org
Subject: Files related to live migration in xen source code
Date: Wed, 20 Mar 2013 10:35:52 +0530 [thread overview]
Message-ID: <CAJoHm3dyH3_tapF=CbUved-6KJL6JVvrAov9ksQjhsPTA246+Q@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 457 bytes --]
Hello sir/madam,
I am a M.tech. Scholar at MNIT Jaipur, India. I am working on xen live
migration security issues. For the work i need to analyse and make few
changes in the source code of live migration in Xen. Can you please tell me
the name or locations of files that are involved in migration of physical
memory or state of virtual machine during the live migration.
Thanks & Regards
Manoj Kumar Yadav
M. Tech. Computer Engineering
MNIT Jaipur, India
[-- Attachment #1.2: Type: text/html, Size: 585 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
reply other threads:[~2013-03-20 5:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAJoHm3dyH3_tapF=CbUved-6KJL6JVvrAov9ksQjhsPTA246+Q@mail.gmail.com' \
--to=mkycse@gmail.com \
--cc=xen-devel@lists.xen.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).