From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
"Alexander Graf" <agraf@suse.de>,
"Paul Mackerras" <paulus@samba.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH] spapr: support time base offset migration
Date: Thu, 05 Sep 2013 22:09:17 +1000 [thread overview]
Message-ID: <5228746D.3060606@ozlabs.ru> (raw)
In-Reply-To: <1378381352.4321.156.camel@pasglop>
On 09/05/2013 09:42 PM, Benjamin Herrenschmidt wrote:
> On Thu, 2013-09-05 at 19:48 +1000, Alexey Kardashevskiy wrote:
>>>> I do not have pure guest timebase in QEMU and I need it on the destination.
>>>> But I have host timebase + offset to calculate it. And tb_offset is already
>>>> in ppc_tb_t. It looked logical to me to send the existing field and add
>>>> only the missing part.
>>>
>>> I still don't understand. You want the guest visible timebase in the migration stream, no?
>>
>>
>> Yes. I do not really understand the problem here (and I am not playing
>> dump). Do you suggest sending just the guest timebase and do not send the
>> host timebase and the offset (one number instead of two)? I can do that,
>> makes sense, no problem, thanks for the idea.
>
> No, we want to send the guest TB and the corresponding "time of day" so that
> the target can adjust the TB based on how long the migration took.
Nobody is discussing time_of_the_day, it is there and transmitted. The only
question is whether to send host_timebase and tb_offset (2 values) or just
guest timebase (1 value).
--
Alexey
next prev parent reply other threads:[~2013-09-05 12:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 7:31 [Qemu-devel] [RFC PATCH] spapr: support time base offset migration Alexey Kardashevskiy
2013-09-03 8:42 ` Andreas Färber
2013-09-03 9:07 ` Alexey Kardashevskiy
2013-09-03 9:22 ` Andreas Färber
2013-09-04 1:13 ` Alexey Kardashevskiy
2013-09-04 1:27 ` Alexander Graf
2013-09-05 4:30 ` David Gibson
2013-09-05 4:54 ` Alexey Kardashevskiy
2013-09-05 9:16 ` Alexander Graf
2013-09-05 9:48 ` Alexey Kardashevskiy
2013-09-05 9:58 ` Alexander Graf
2013-09-05 11:44 ` Benjamin Herrenschmidt
2013-09-05 12:37 ` Alexander Graf
2013-09-05 13:36 ` Benjamin Herrenschmidt
2013-09-05 13:39 ` Alexander Graf
2013-09-05 14:14 ` Andreas Färber
2013-09-05 14:26 ` Benjamin Herrenschmidt
2013-09-05 15:11 ` Alexander Graf
2013-09-09 2:40 ` Alexey Kardashevskiy
2013-09-09 5:50 ` Alexander Graf
2013-09-09 5:58 ` Alexey Kardashevskiy
2013-09-09 6:06 ` Alexander Graf
2013-09-09 9:29 ` Benjamin Herrenschmidt
2013-09-09 9:32 ` Alexander Graf
2013-09-09 9:38 ` Benjamin Herrenschmidt
2013-09-09 9:41 ` Alexander Graf
2013-09-13 5:20 ` David Gibson
2013-09-13 18:06 ` Alexander Graf
2013-09-05 11:42 ` Benjamin Herrenschmidt
2013-09-05 12:09 ` Alexey Kardashevskiy [this message]
2013-09-06 3:00 ` David Gibson
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=5228746D.3060606@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).