This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: OHMURA Kei
Signed-off-by: Yoshiaki Tamura
---
Makefile.objs
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
Makefile.objs
Juan:
It's especailly important for ft to be a standalone thread, as it
may cause monitor to be blocked by network problems. what's your
schedule, maybe I can help some.
Yoshi:
in the following code:
+
+s->file = qemu_fopen_ops(s, ft_trans_put_buffer, ft_trans_get_buffer,
+
2011/2/24 Juan Quintela :
>
> [ trimming cc to kvm & qemu lists]
>
> Yoshiaki Tamura wrote:
>> Juan Quintela wrote:
>>> Yoshiaki Tamura wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
[ trimming cc to kvm & qemu lists]
Yoshiaki Tamura wrote:
> Juan Quintela wrote:
>> Yoshiaki Tamura wrote:
>>> This code implements VM transaction protocol. Like buffered_file, it
>>> sits between savevm and migration layer. With this architecture, VM
>>> transaction protocol is implemented m
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
Makefile.objs
Juan Quintela wrote:
Yoshiaki Tamura wrote:
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Could you explain what is the
Yoshiaki Tamura wrote:
> This code implements VM transaction protocol. Like buffered_file, it
> sits between savevm and migration layer. With this architecture, VM
> transaction protocol is implemented mostly independent from other
> existing code.
Could you explain what is the difference with
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
Makefile.objs
2011/2/23 ya su :
> Yoshi:
>
> thanks for your explaining.
> if you introduce a new stage as 3, I think stage 1 also need to change as
> it will mark all pages dirty.
> looking forward to your new patch update.
Unless there're strong comments from others, I won't put it in
this series tho
Hi Green,
2011/2/21 ya su :
> Yoshiaki:
>
> I have one question about ram_save_live, during migration 3
> stage(completation stage), it will call
> cpu_physical_memory_set_dirty_tracking(0) to stop recording ram dirty pages.
> at the end of migrate_ft_trans_connect function, it will invoke vm_
This code implements VM transaction protocol. Like buffered_file, it
sits between savevm and migration layer. With this architecture, VM
transaction protocol is implemented mostly independent from other
existing code.
Signed-off-by: Yoshiaki Tamura
Signed-off-by: OHMURA Kei
---
Makefile.objs
12 matches
Mail list logo