From: Marc Zyngier <marc.zyngier@arm.com>
To: Miriam Zimmerman <mutexlox@google.com>
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: Timekeeping on ARM guests/hosts
Date: Thu, 11 Oct 2018 08:54:28 +0100 [thread overview]
Message-ID: <86lg74ude3.wl-marc.zyngier@arm.com> (raw)
In-Reply-To: <CAHSjozBtan6L7eWypnB_aACqHSrBAykjU8LcxfM3Pv3QMSZnJw@mail.gmail.com>
Hi Miriam,
On Wed, 10 Oct 2018 19:38:47 +0100,
Miriam Zimmerman <mutexlox@google.com> wrote:
>
> (oops, sorry for lack of plaintext in the first email. must've
> forgotten to click the button in my email client)
>
> Until that happens, what's the best workaround? Just running an ntp
> daemon in guest?
Christoffer reminded me yesterday that stolen time accounting only
affects scheduling, and is not evaluated for
An NTP daemon may not be the best course of action, as the guest is
going to see a massive jump anyway, which most NTP implementations are
not design to handle (they rightly assume that something else is
wrong). It would also mean that you'd have to run a NTP server
somewhere on the host, as you cannot always assume full connectivity.
A popular way to solve this seems to be using the QEMU guest agent,
but I must admit I never really investigated that side of the problem.
I'm quite curious of how this is done on x86 though. KVM_GUEST mostly
seems to give the guest a PV clocksource, which is not going to help in
terms of wall clock. Do you have any idea?
Thanks,
M.
>
> On Wed, Oct 10, 2018 at 3:01 AM Marc Zyngier <marc.zyngier@arm.com> wrote:
> >
> > Hi Myriam,
> >
> > On 10/10/18 00:39, Miriam Zimmerman wrote:
> > > Hi,
> > >
> > > I'm working with an ARM device hosting an ARM guest. When the host is
> > > suspended, guest time stops advancing and it doesn't get adjusted on resume.
> >
> > I know the feeling, my arm64 laptop gives me that kind of grief all the
> > time... :-/
> >
> > > For an x86 machine, the CONFIG_KVM_GUEST flag would enable paravirt for
> > > time and fix this problem, but CONFIG_KVM_GUEST isn't available on ARM.
> > >
> > > Is there a configuration option to enable paravirtualized timekeeping on
> > > ARM? If not, how can I configure ARM guests to handle timekeeping properly?
> >
> > PV time (or rather stolen time) is a work in progress at the moment, and
> > Christoffer has his hands in that particular pie.
> >
> > Thanks,
> >
> > M.
> > --
> > Jazz is not dead. It just smells funny...
--
Jazz is not dead, it just smell funny.
next prev parent reply other threads:[~2018-10-11 7:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 23:39 Timekeeping on ARM guests/hosts Miriam Zimmerman
2018-10-10 10:01 ` Marc Zyngier
2018-10-10 18:38 ` Miriam Zimmerman
2018-10-11 7:54 ` Marc Zyngier [this message]
2018-10-11 15:21 ` Laszlo Ersek
2018-10-11 18:40 ` Miriam Zimmerman
2018-10-31 16:41 ` Steven Price
2018-10-31 18:49 ` Miriam Zimmerman
2018-11-02 14:34 ` Christoffer Dall
2018-11-02 18:28 ` Miriam Zimmerman
2018-11-02 21:23 ` Miriam Zimmerman
2018-11-06 7:45 ` Christoffer Dall
2018-11-06 13:39 ` Alex Bennée
2018-11-06 18:37 ` Miriam Zimmerman
2018-11-07 9:42 ` Christoffer Dall
2018-11-07 18:22 ` Miriam Zimmerman
2018-11-08 10:26 ` Christoffer Dall
2018-11-08 16:34 ` Steven Price
2018-11-08 20:06 ` Christoffer Dall
2018-11-03 0:19 ` Bijan Mottahedeh
2018-11-06 7:49 ` Christoffer Dall
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=86lg74ude3.wl-marc.zyngier@arm.com \
--to=marc.zyngier@arm.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=mutexlox@google.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