From: Bechir Bani <bechir.bani@gmail.com>
To: Sanidhya Kashyap <sanidhya.iiith@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Qemu live migration code
Date: Mon, 24 Mar 2014 16:40:00 -0400 [thread overview]
Message-ID: <CACpvL08Pe7GhmrRwtk-HjgzQyobPNX2+MvevzNG8ORHCmQFbow@mail.gmail.com> (raw)
In-Reply-To: <CAAUTuqAQLYRZ++6EFUuwaTKKv2qmagLcSrPrTBusdJYuCrB4tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hi Sanidhya,
Which function in savevm.c can tell me about the stop time ?
2014-03-24 13:46 GMT-04:00 Sanidhya Kashyap <sanidhya.iiith@gmail.com>:
> savevm.c will tell you about the stop time.
>
> arch_init.c (ram_save_block) will tell about the number of pages
> transferred.
>
>
> On Mon, Mar 24, 2014 at 10:51 PM, Bechir Bani <bechir.bani@gmail.com>wrote:
>
>> I have a task to add trace points in the source code of Qemu. The goal is
>> to know the number of pages transferred at each iteration and stop time of
>> the machine as well.
>>
>>
>> 2014-03-24 12:50 GMT-04:00 Dr. David Alan Gilbert <dgilbert@redhat.com>:
>>
>> * Bechir Bani (bechir.bani@gmail.com) wrote:
>>> > Hi,
>>> >
>>> > I want to know the source code of qemu which is responsible for the
>>> > migration of virtual machines, more precisely where the part of the
>>> code
>>> > that describes the stages of memory transfer. is that you can help me?
>>>
>>> It's split around a few files; memory is mostly in arch_init.c;
>>> It's something like:
>>>
>>> migration.c Overall management
>>> savevm.c
>>> qemu-file.c File buffering/bytes on the wire
>>> vmstate.c Structured saving of individual devices
>>> arch_init.c RAM special code, and a few other things
>>>
>>> What are you trying to do/change?
>>>
>>> Dave
>>>
>>> --
>>> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
>>>
>>
>>
>>
>> --
>> *Béchir Bani *
>> ****************************************************************
>> *Ecole Polytechnique de Montréal *
>> ****************************************************************
>> *Laboratoire DORSAL*
>> *****************************************************************
>> *Montréal - Canada*
>>
>
>
--
*Béchir Bani *
****************************************************************
*Ecole Polytechnique de Montréal *
****************************************************************
*Laboratoire DORSAL*
*****************************************************************
*Montréal - Canada*
[-- Attachment #2: Type: text/html, Size: 3679 bytes --]
next prev parent reply other threads:[~2014-03-24 20:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 15:29 [Qemu-devel] Qemu live migration code Bechir Bani
2014-03-24 15:33 ` 陈梁
2014-03-24 16:50 ` Dr. David Alan Gilbert
2014-03-24 17:21 ` Bechir Bani
2014-03-24 17:46 ` Sanidhya Kashyap
2014-03-24 20:40 ` Bechir Bani [this message]
2014-03-25 10:03 ` Sanidhya Kashyap
2014-05-12 16:03 ` Bechir Bani
2014-05-13 8:05 ` 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=CACpvL08Pe7GhmrRwtk-HjgzQyobPNX2+MvevzNG8ORHCmQFbow@mail.gmail.com \
--to=bechir.bani@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=sanidhya.iiith@gmail.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).