From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID,
	DKIM_VALID_AU,FREEMAIL_FROM,T_SCC_BODY_TEXT_LINE autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 26521 invoked from network); 5 Feb 2022 17:42:33 -0000
Received: from 4ess.inri.net (216.126.196.42)
  by inbox.vuxu.org with ESMTPUTF8; 5 Feb 2022 17:42:33 -0000
Received: from mail-lf1-f49.google.com ([209.85.167.49]) by 4ess; Sat Feb  5 12:34:11 -0500 2022
Received: by mail-lf1-f49.google.com with SMTP id z4so18860013lft.3
        for <9front@9front.org>; Sat, 05 Feb 2022 09:34:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20210112;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to;
        bh=vVzpwxqSqxhA4F0oetw8aB0dtDRq8atdSSJWt2bacOY=;
        b=Nud0VDrt6IrADSIbeMa+LKu8yFBsbtKsL1DVo1lAyU0VKzVcygBHjSbn9cx+uqwG4r
         gzbI8GD6lkfeXK9tP4SXnISPfxs8XzMm7XSAynFRQz/HH7jGQIahcrLA7uND7JNmopnL
         vIZeOWKAyBUFEAV4KE4akEULijLR7ztm+dZcMR81L2VBVyIonhLyLu36zzGJ5bqA2IAT
         v0QAY1AW5ih/eddVkFlpE/5HG43MSeoM4YaiTy4XAy/L09OAee0pdHiTvNLTnmQ3+Trq
         2EErodugrRxIpWDbtM0qQMsdfxqu+I9Ok6WLKIxLRbvbvby2kNOFKqUjI+qPgAu1b2ee
         gdiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=x-gm-message-state:mime-version:in-reply-to:references:from:date
         :message-id:subject:to;
        bh=vVzpwxqSqxhA4F0oetw8aB0dtDRq8atdSSJWt2bacOY=;
        b=aqYG5HDjVaV2gPNWAiL1/86lviQo1D3LQe6Y6sPoK8RxCedm4O9gZuHhkwsV2CPYvm
         Dv7snX4Yurw+V4fNHrGhNRpZDh+8dRvmDOyFYwQxIzF4XaJrT94YHxpZ9LDw4uG5zDdF
         MOOF4sQXxBw6eqxG2DeBB/+2JZFnPJCvzUra8m8/GKHMlJ7vMRtrVzbaaurGeGblZBPE
         VTruw3bxeh5RLF+ijS8B8iHH2NxPAvZr/sfrWZOAIHTk914K/ZlbDj6aiyCkV/VpljDH
         XXdHpY03AkpK/lQVHZohLbFB4IMIz2SayoBURnS0oSpoA7UDxOTE0dXh2ppUBxkWYkpA
         s8jA==
X-Gm-Message-State: AOAM532qGH9HL7AYHecsgoFoKx4K5WwT4eQXw/rAlK1c3od+kaubcpia
	OphWpLl2gr5LEomcEPGS3O+XuU9qG93W7yBKSCOiXRLi3RA=
X-Google-Smtp-Source: ABdhPJz9xKn8LDQOU4KVFTCdoMY9P6ZvTorVEHAYc1XYompjy6cCg87OqUYpzsW9+HqDYK7b5vLS+YU3MLj/MOANklk=
X-Received: by 2002:a17:906:9b87:: with SMTP id dd7mr3933199ejc.758.1644080657246;
 Sat, 05 Feb 2022 09:04:17 -0800 (PST)
MIME-Version: 1.0
Received: by 2002:a54:26cb:0:0:0:0:0 with HTTP; Sat, 5 Feb 2022 09:04:16 -0800 (PST)
In-Reply-To: <CAGw6cBvo+bA9BCOdXtM8O6vezod1szmVgKj0g-YnNYagf5++hw@mail.gmail.com>
References: <CAGw6cBvo+bA9BCOdXtM8O6vezod1szmVgKj0g-YnNYagf5++hw@mail.gmail.com>
From: hiro <23hiro@gmail.com>
Date: Sat, 5 Feb 2022 18:04:16 +0100
Message-ID: <CAFSF3XMXafw5Fvugd8ZFMvGvCrise-_XznyKVj=cUdSpofqS-A@mail.gmail.com>
To: 9front@9front.org
Content-Type: text/plain; charset="UTF-8"
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: virtualized element-aware table table 
Subject: Re: [9front] qemu clock/timer issue
Reply-To: 9front@9front.org
Precedence: bulk

do you have timesync running twice? check in ps output.

On 2/5/22, Michael Forney <mforney@mforney.org> wrote:
> I was recently running 9front in a VM on linux (qemu, with
> -enable-kvm), and noticed several weird timing/clock issues. The date
> command gives wildly varying results +- 1 minute:
>
> cpu% date
> Fri Feb  4 17:39:23 PST 2022
> cpu% date
> Fri Feb  4 17:39:12 PST 2022
> cpu% date
> Fri Feb  4 17:40:19 PST 2022
> cpu% date
> Fri Feb  4 17:39:18 PST 2022
>
> `sleep 1` exits pretty much instantly, stats moves through the entire
> width in a second or two, and clicking in scrollbars starts repeating
> immediately.
>
> I notice the following messages in my dmesg:
> kvm: vcpu 3: requested 38141 ns lapic timer period limited to 200000 ns
> kvm: vcpu 1: requested 9449 ns lapic timer period limited to 200000 ns
> kvm: vcpu 2: requested 51204 ns lapic timer period limited to 200000 ns
> kvm: vcpu 0: requested 74421 ns lapic timer period limited to 200000 ns
>
> I don't remember this problem last time I ran 9front in qemu (around a
> year ago), so I looked through commit history and found one commit
> that seemed like it might be related:
> http://git.9front.org/plan9front/plan9front/a05bab362f66ddd6fa65f2e7cda9eaaa0217ec08/commit.html
>
> To check, I tried setting *nohpet=1 in my plan9.ini, which *seems* to
> have solved the problem, though I still see those same messages in
> dmesg on the linux host (but now the requested lapic timer period is
> always around 100000 ns or greater).
>
> Anyone know what's going on here?
>