From: Yoshiaki Tamura <tamura.yoshiaki@lab.ntt.co.jp>
To: Avi Kivity <avi@redhat.com>
Cc: Gleb Natapov <gleb@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: Question on skip_emulated_instructions()
Date: Thu, 08 Apr 2010 17:30:08 +0900 [thread overview]
Message-ID: <4BBD9410.1090208@lab.ntt.co.jp> (raw)
In-Reply-To: <4BBD87A2.5000909@redhat.com>
Avi Kivity wrote:
> On 04/08/2010 10:30 AM, Yoshiaki Tamura wrote:
>>
>> To answer your question, it should be possible to implement.
>> The down side is that after going into KVM to make the guest state to
>> consistent, we need to go back to qemu to actually transfer the guest,
>> and this bounce would introduce another overhead if I'm understanding
>> correctly.
>
> Yes. It should be around a microsecond or so, given you will issue I/O
> after this I don't think this will affect performance.
That is a good news.
>> And yes, all I need is some consistent state to resume VM from, which
>> must be able to continue I/O operations, like writing to disks and
>> sending ack over the network. If I can guarantee this, sending the VM
>> state after completing output is acceptable.
>>
>
> I suggest you start with this. If it turns out performance is severely
> impacted, we can revisit instruction completion. If performance is
> satisfactory, then we'll be able to run Kemari with older kernels.
I was almost to say yes here, but let me ask one more question.
BTW, thank you two for taking time for this discussion which isn't a topic on
KVM itself.
If I transferred a VM after I/O operations, let's say the VM sent an TCP ACK to
the client, and if a hardware failure occurred to the primary during the VM
transferring *but the client received the TCP ACK*, the secondary will resume
from the previous state, and it may need to receive some data from the client.
However, because the client has already receiver TCP ACK, it won't resend the
data to the secondary. It looks this data is going to be dropped. Am I missing
some point here?
next prev parent reply other threads:[~2010-04-08 8:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 4:11 Question on skip_emulated_instructions() Yoshiaki Tamura
2010-04-06 10:05 ` Gleb Natapov
2010-04-07 6:25 ` Yoshiaki Tamura
2010-04-07 15:43 ` Gleb Natapov
2010-04-07 17:21 ` Yoshiaki Tamura
2010-04-07 17:37 ` Avi Kivity
2010-04-08 5:27 ` Yoshiaki Tamura
2010-04-08 5:41 ` Gleb Natapov
2010-04-08 6:18 ` Yoshiaki Tamura
2010-04-08 6:56 ` Gleb Natapov
2010-04-08 7:30 ` Yoshiaki Tamura
2010-04-08 7:37 ` Avi Kivity
2010-04-08 8:30 ` Yoshiaki Tamura [this message]
2010-04-08 8:38 ` Avi Kivity
2010-04-08 7:17 ` Avi Kivity
2010-04-08 7:19 ` Gleb Natapov
2010-04-08 8:10 ` Yoshiaki Tamura
2010-04-08 8:40 ` Avi Kivity
2010-04-08 9:14 ` Yoshiaki Tamura
2010-04-08 11:49 ` Avi Kivity
2010-04-08 13:42 ` Yoshiaki Tamura
2010-04-08 13:47 ` Avi Kivity
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=4BBD9410.1090208@lab.ntt.co.jp \
--to=tamura.yoshiaki@lab.ntt.co.jp \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.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