From: Avi Kivity <avi@redhat.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] allow userspace to adjust kvmclock offset
Date: Thu, 15 Oct 2009 09:46:52 +0900 [thread overview]
Message-ID: <4AD670FC.7010004@redhat.com> (raw)
In-Reply-To: <20091013124638.GC8092@mothafucka.localdomain>
On 10/13/2009 09:46 PM, Glauber Costa wrote:
> On Tue, Oct 13, 2009 at 03:31:08PM +0300, Avi Kivity wrote:
>
>> On 10/13/2009 03:28 PM, Glauber Costa wrote:
>>
>>>
>>>> Do we want an absolute or relative adjustment?
>>>>
>>>>
>>> What exactly do you mean?
>>>
>>>
>> Absolute adjustment: clock = t
>> Relative adjustment: clock += t
>>
> The delta is absolute, but the adjustment in the clock is relative.
>
> So we pick the difference between what userspace is passing us and what
> we currently have, then relatively adds up so we can make sure we won't
> go back or suffer a too big skew.
>
The motivation for relative adjustment is when you have a jitter
resistant place to gather timing information (like the kernel, which can
disable interrupts and preemption), then pass it on to kvm without
losing information due to scheduling. For migration there is no such
place since it involves two hosts, but it makes sense to support
relative adjustments.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-10-15 0:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 17:24 [PATCH] allow userspace to adjust kvmclock offset Glauber Costa
2009-10-12 8:53 ` Avi Kivity
2009-10-13 12:28 ` Glauber Costa
2009-10-13 12:31 ` Avi Kivity
2009-10-13 12:46 ` Glauber Costa
2009-10-15 0:46 ` Avi Kivity [this message]
2009-10-15 14:58 ` Glauber Costa
2009-10-22 16:23 ` 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=4AD670FC.7010004@redhat.com \
--to=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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).