Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3725035ybl; Mon, 12 Aug 2019 05:27:19 -0700 (PDT) X-Google-Smtp-Source: APXvYqwz1GG+CV5Zk7vvoKvHwAl8jOlkkmWYP1JEYMoHOhSU0GyZCLKxcitoHZ6CEyXyAaCYAUYK X-Received: by 2002:a17:90a:94c3:: with SMTP id j3mr5221983pjw.10.1565612839434; Mon, 12 Aug 2019 05:27:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565612839; cv=none; d=google.com; s=arc-20160816; b=00x+Jr4qD2YHm3Bp5ip1PPiuQ8B6rAt7OtAu0zLJbhKrQ16ZGl+O2y4sPgkQPkqqFF /GyqbXl6AninVtL8dodYXncCQ/kuaUloK9OdK7CETtxyH/DmoH7uIN7lpDtepXvtv3KV NBHfiCzWlFjXQZhYx8AaC/PR3wOII6s146XJtB/pExInlLGIzpFdTV/4D8LJGyGkQKru z2yRGSCHaO9dqMGb1C7JeNDn8mcxkIVKMyVk/+tfIAekuA5HF95N7ov8YfGBV6HO5xTg 8fOZL3GesLzhAqgb++COMnemccY8PMSpgAq23AKqLdWH5+RqkmecuqS1R9aDQXhgXWtr 7fAA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date; bh=9tKLa746ytge5B2KSmxV5rUZARaUDxpY2ZklFxyCkQU=; b=YpUDjI8iivdwlSH119kLN9NaWgFNhSNgTxaUfvLDclcQBg+kGKrkepvTH7B1sL419v lVCLZFCKSUsOOJv6aksnMBxfg+sZeRyz5W3BQD3NPpqCn7k8Z2A187oPHGSsbBCxbkvL 9jE2Dc+Ca6yTGhS8vn7rTj9+Q7QAkAvL2aHQQw5PIjZ2f/UnexM0JqCZcW22Z1RtHD/O V2U1gUzdcADnaoz2M1tg4e0istUoS0+mx0WnyBEB7d1Hgv978/FhEjVuDS1gdOOMibQ8 UHqsVtkSM0CVLiTT8F0gxOrodirP3SK9eE0mfUA8D3ErArB6gsKu+okwt2c1G0VImdnT ZXCw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j1si65433474pfa.91.2019.08.12.05.27.04; Mon, 12 Aug 2019 05:27:19 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728776AbfHLMYs (ORCPT + 99 others); Mon, 12 Aug 2019 08:24:48 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:59870 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728384AbfHLMYq (ORCPT ); Mon, 12 Aug 2019 08:24:46 -0400 Received: from p200300ddd71876867e7a91fffec98e25.dip0.t-ipconnect.de ([2003:dd:d718:7686:7e7a:91ff:fec9:8e25]) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1hx9NI-0003qj-7W; Mon, 12 Aug 2019 14:24:32 +0200 Date: Mon, 12 Aug 2019 14:24:25 +0200 (CEST) From: Thomas Gleixner To: "Li, Aubrey" cc: "Lendacky, Thomas" , Daniel Drake , "x86@kernel.org" , "H . Peter Anvin" , Linux Kernel , Endless Linux Upstreaming Team , Jiri Slaby Subject: Re: [PATCH] x86/apic: Handle missing global clockevent gracefully In-Reply-To: <1803ad97-74f4-28c6-58c8-c52b3d1e5b1f@linux.intel.com> Message-ID: References: <81666b28-d029-56c3-8978-90abc219d1b7@linux.intel.com> <3d14b0cc-3cca-1874-3521-4ee2ec52141d@amd.com> <5bf28ba4-b7c1-51de-88ae-feebae2a28db@amd.com> <75e59ac6-5165-bd0a-aec9-be16d662ece9@amd.com> <1803ad97-74f4-28c6-58c8-c52b3d1e5b1f@linux.intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 12 Aug 2019, Li, Aubrey wrote: > On 2019/8/9 20:54, Thomas Gleixner wrote: > > + local_irq_disable(); > > /* > > * Setup the APIC counter to maximum. There is no way the lapic > > * can underflow in the 100ms detection time frame > > */ > > __setup_APIC_LVTT(0xffffffff, 0, 0); > > > > - /* Let the interrupts run */ > > - local_irq_enable(); > > + /* > > + * Methods to terminate the calibration loop: > > + * 1) Global clockevent if available (jiffies) > > + * 2) TSC if available and frequency is known > > + */ > > + jif_start = READ_ONCE(jiffies); > > + > > + if (tsc_khz) { > > + tsc_start = rdtsc(); > > + tsc_perj = div_u64((u64)tsc_khz * 1000, HZ); > > + } > > + > > + while (lapic_cal_loops <= LAPIC_CAL_LOOPS) { > > Is this loop still meaningful, can we just invoke the handler twice > before and after the tick? And that solves what? > Thanks, > -Aubrey Can you please trim your replies? Thanks, tglx