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.0 required=5.0 tests=T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30001 invoked from network); 21 Feb 2022 22:40:14 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 21 Feb 2022 22:40:14 -0000 Received: from duke.felloff.net ([216.126.196.34]) by 4ess; Mon Feb 21 17:35:40 -0500 2022 Message-ID: Date: Mon, 21 Feb 2022 23:35:31 +0100 From: cinap_lenrek@felloff.net To: 9front@9front.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: shader app-based grid-scale configuration-based controller Subject: Re: [9front] qemu clock/timer issue Reply-To: 9front@9front.org Precedence: bulk Nice writeup. Thank you for this investigation. > Maybe this is something I need to ask qemu developers. Yes, please try. Maybe we are missing some instruction barriers when reading the tsc counter? The issue is hard to reproduce for me, i have no issues with qemu or real hardware. I guess it also depends on the host cpu and linux scheduling and the moon phase :( Anyway, dont give up. It would be very nice to get to the bottom of this. -- cinap