Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp4442625ybb; Tue, 14 Apr 2020 07:25:39 -0700 (PDT) X-Google-Smtp-Source: APiQypLPbGZMzckdqM5NOyjEL8zbfJs0lWFXukMlMQkJXOSU+gHwtn6PipeVBxvUVD61Zh+34pNd X-Received: by 2002:a05:6402:1bc4:: with SMTP id ch4mr21408426edb.80.1586874339116; Tue, 14 Apr 2020 07:25:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586874339; cv=none; d=google.com; s=arc-20160816; b=IuvJvwYsZ5E0LQ2mdAqGZcz2xSVFMdxQgeLwL57IBQDcsw48YKeQkcUw64RO8nUJ7O 1tinCwZScgzt+UOIj09T1fqLHdKXsVkwd+0Nj4GkWL0Cn90AcUJyHK0AtdfBo6eRcAz+ 5LBSIfMPmm6UiIYP2L0edm8KFxvqaAB3A4f+Sc64hqIBJ70xf3OaE1zqGi5QcISDW2+2 jKNS7dcxVx+aIcgJgt9w2y+q2s54b5s9W2TqGaigz0eQdbN6n0lD6WOqlikTJ1lFG7Wn ATfQOHPV60MGyiNg710Y1ZigA5pp22x1dMqy7Y1TPK8gKlWenj9JM+Jf7x4wdB5cOAE7 Epcg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=Qbr2piWjuUos1T4WJ4VfnNByALInee9nCK8GhQpNQ50=; b=KuP6dUZp9kjMTYMiojmamvvY4ja6VGKYWwQotATTOzvObyP2vljdSJEnUkCyD9U0Gl KjLw6hkRrqAWfBLYoDVBXuTqw9UQrcwU6K2YYCnLCPSLecX5w0nFzVLfawBK1+LGJhxG bi9c0GLvhe31Wn1xmAY6Z+ukuVDyoYa5F8LQTzOS8v2LAu5ZUfTPvzsaOWHKincg0p0M LFYf68mPUnj2yF3xqDISB6Dh8cD3McMye2re3NNzP7JOE+7Xl8gfFO1OMLasV9aqv+Nz boWq/2z5Cv9hKKkcAUQr2IylKlTahjyZPXqpcrEor+9XF7pAhXFX9vtBIDfkGEbmcuwJ /ENQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=fiurNNKw; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id jz18si8267007ejb.112.2020.04.14.07.25.14; Tue, 14 Apr 2020 07:25:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@zx2c4.com header.s=mail header.b=fiurNNKw; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=zx2c4.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2405314AbgDNEVY (ORCPT + 99 others); Tue, 14 Apr 2020 00:21:24 -0400 Received: from mail.zx2c4.com ([192.95.5.64]:38217 "EHLO mail.zx2c4.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2405226AbgDNEVX (ORCPT ); Tue, 14 Apr 2020 00:21:23 -0400 Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTP id ccc82e8a; Tue, 14 Apr 2020 04:11:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=zx2c4.com; h=mime-version :references:in-reply-to:from:date:message-id:subject:to:cc :content-type; s=mail; bh=ZHWdBzlGnU+TSQ/OY85/9pN0jDk=; b=fiurNN Kwg16EZkR6R765OwLLIDKvf2oVNVqv2Ovz/LbiC3xx9U4sIgVeDV3ARR1vVLROzh yA+9rqpAtjnNIpkaGDLRmQs2PUy/rfM7AS6uRXQhy8EpS9OMrXwPFP+ve1lbrbnN JE5D8A/P5qCqCcWQ+TUOYt5dR9FRfh4qya1pfoWuNkZsuJRhTnFca34XVFeU1m00 IIeh/js5kE23MnFToIUX9YeesGlT5IXVVJTRYGaGx+pi2m5qU5WZsgRbU6GwHNyg MiKwWHkfOsjevH/I4zfc9hqrM+wCrfpRC7Xckxe/LJiBoJunEYuKfzVo+smA9+8a Hitxb1aXk2bMnOmw== Received: by mail.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id 88974827 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Tue, 14 Apr 2020 04:11:33 +0000 (UTC) Received: by mail-il1-f174.google.com with SMTP id f82so7335232ilh.8; Mon, 13 Apr 2020 21:21:20 -0700 (PDT) X-Gm-Message-State: AGi0Puag5qXIieN6iBh2lkiZGdyr/wx2ibzn7vFs1oKsFfUa9cpr/Xwb S8JG+s8vjbCtFMkt/TTeK9IXTvsDKmR9iRLI+yE= X-Received: by 2002:a92:d98c:: with SMTP id r12mr2063647iln.224.1586838079492; Mon, 13 Apr 2020 21:21:19 -0700 (PDT) MIME-Version: 1.0 References: <20200407063345.4484-1-Jason@zx2c4.com> <20200407063345.4484-3-Jason@zx2c4.com> <0e189a4fe1e69b08afc859ce83623a0e5ea0c08b.camel@linux.intel.com> In-Reply-To: <0e189a4fe1e69b08afc859ce83623a0e5ea0c08b.camel@linux.intel.com> From: "Jason A. Donenfeld" Date: Mon, 13 Apr 2020 22:21:08 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 3/3] x86/mce/therm_throt: allow disabling the thermal vector altogether To: Srinivas Pandruvada Cc: LKML , linux-edac@vger.kernel.org, X86 ML , Arnd Bergmann , bberg@redhat.com, bp@suse.de Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 13, 2020 at 9:38 PM Srinivas Pandruvada wrote: > > On Tue, 2020-04-07 at 00:33 -0600, Jason A. Donenfeld wrote: > > The thermal IRQ handler uses 1.21% CPU on my system when it's hot > > from > > compiling things. Indeed looking at /proc/interrupts reveals quite a > > lot > I am curious why you are hitting threshold frequently? > What is rdmsr 0x1a2 5640000 > > of events coming in. Beyond logging them, the existing drivers on the > > system don't appear to do very much that I'm interested in. So, add a > > way to disable this entirely so that I can regain precious CPU > > cycles. > It is showing amount of time system is running in a constrained > environment. Lots of real time and HPC folks really care about this. Which is why this patch adds an option, not a full removal or something. Real time and HPC people can keep their expensive interrupt. Other people with different varieties of system can disable it.