From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 070E5C624D7 for ; Wed, 2 Sep 2026 08:05:29 +0000 (UTC) Received: from list by lists.xenproject.org with outflank-mailman.1405278.1638802 (Exim 4.92) (envelope-from ) id 1x1fy6-0004t3-MR; Wed, 02 Sep 2026 08:05:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 1405278.1638802; Wed, 02 Sep 2026 08:05:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1x1fy6-0004sw-Jf; Wed, 02 Sep 2026 08:05:14 +0000 Received: by outflank-mailman (input) for mailman id 1405278; Wed, 02 Sep 2026 08:05:13 +0000 Received: from mail.xenproject.org ([104.130.215.37]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1x1fy5-0004sQ-G8 for xen-devel@lists.xenproject.org; Wed, 02 Sep 2026 08:05:13 +0000 Received: from xenbits.xenproject.org ([104.239.192.120]) by mail.xenproject.org with esmtp (Exim 4.96) (envelope-from ) id 1x1fy4-001oEa-1a; Wed, 02 Sep 2026 08:05:12 +0000 Received: from 224.pool85-54-217.dynamic.orange.es ([85.54.217.224] helo=localhost) by xenbits.xenproject.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x1fy3-000zVN-2w; Wed, 02 Sep 2026 08:05:12 +0000 X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=xenproject.org; s=20200302mail; h=In-Reply-To:Content-Transfer-Encoding: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=8AxFR/Dq80dQVj014nchVr+oA3GHFCApYN4dOpMUvak=; b=IoUAgxK6IyW/9J9hHFU+vrx8B+ kFxEXm8gs/SoZx5CX9VjQeynChgmuYcHNstIoYdLzPN0ahlC82e4SpntF5DF91kDf6AKt8OCwmnLM iSRoWfxJzwyUy1vlqKz7jYsT2oGEXlEonERd6qpC1rb1USHkSADVaFF1hMO/o97SH+6E=; Date: Wed, 2 Sep 2026 10:05:03 +0200 From: Roger Pau =?utf-8?B?TW9ubsOp?= To: Jan Beulich Cc: "xen-devel@lists.xenproject.org" , Andrew Cooper , Julien Grall , Stefano Stabellini , Anthony PERARD , Michal Orzel Subject: Re: [PATCH v2 2/4] time: shorten year determination loop Message-ID: References: <79d50725-3892-4643-b854-bfec9c0c0d79@suse.com> <7bed7164-9a53-4e53-9fc1-7af68108bdf8@suse.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: On Thu, Jul 02, 2026 at 11:30:11AM +0200, Jan Beulich wrote: > For dates very far into the future (the MC146818 RTC's century byte can go > up to the 99th century), the present year-wise loop would become somewhat > inefficient (taking perhaps several thousand iterations). Prefix that loop > with a 400-year granular calculation (somewhat like the earlier loop does > for dates in the past). > > Signed-off-by: Jan Beulich Acked-by: Roger Pau Monné Thanks, Roger.