Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp978151ybc; Tue, 12 Nov 2019 12:10:59 -0800 (PST) X-Google-Smtp-Source: APXvYqxVuz6ipspfCJ7ANcdEyQ2fc4M8dB/3YrF6UoeRfA9cjM0yzyv5T7AvKxsWGu49GmHu/s3U X-Received: by 2002:a17:906:3ec2:: with SMTP id d2mr30715730ejj.251.1573589459650; Tue, 12 Nov 2019 12:10:59 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573589459; cv=none; d=google.com; s=arc-20160816; b=cgTlZy3hkzo4GidOnCqsGgpwa+40GdZ+0hKYmR+hA11frezuspiWKC0ZwX0fqU1LcK ZTnuvANDsycf8SM43E7ugvjaWwaYUoHVI3Tft3rwPknzpgqluQ1niOF68jV5rfj6Qz9v hmmgHpW9/kxydKlEJvAWD+KO7GnPBlKecyIV5bJGXtc65xLgT3X/hBMaMpoi9+O0zqTO sNIIFlgU4h06Dww8RdG7x4nLXN5DziFyneOm8tK/V+0sd03oHD0C//HGcqGtZK1+JK+m VTfan+sgvWztlECY7+z1/LWEeMRBsJHKizvomoxEpPa0nbM2ImbOa7cYmYm7K+AMpX6i XLLg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:organization:in-reply-to :content-disposition:mime-version:references:message-id:subject:to :from:date; bh=JW66xjcWp+4Fm8qDY+CqsZmNSkcneDK0RJaWHlsBjYM=; b=Tg0b0HwMOKqyUgRZSqeCIhoVexshCyRzVwxcdRy+Aw2gtjS04v2EbG41JSW8riE8Ai 7ceHvNJU0KlPB2jDxeD7qSAYZSsQvveQGRWQma4qVFUQDRcw2kewCH9Ysyf4o8pwn+TE I0RmeIhO4KHf6pBC1ocCvCjOUyiD+66R5e+HNN6xWAT7Br9bhEurkT6kUbe0t2fcWtEq VGtvpn4MGrwU1NyFYij75ApRTqvmBLZoXzN4l7inflCt1vz0u8YXqo9NsbNvvQUpGc/+ IWSbkuorR7Iz9Xax8W9mOoAZGgOyn1AbaL2fuiNpb+1AgtG2KWy1ohqpeGirza2Fg0pq nCtA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y31si14209583edb.47.2019.11.12.12.10.35; Tue, 12 Nov 2019 12:10:59 -0800 (PST) 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726936AbfKLUHI (ORCPT + 99 others); Tue, 12 Nov 2019 15:07:08 -0500 Received: from mga01.intel.com ([192.55.52.88]:16115 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726008AbfKLUHI (ORCPT ); Tue, 12 Nov 2019 15:07:08 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Nov 2019 12:07:07 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,297,1569308400"; d="scan'208";a="198206403" Received: from joshbuck-mobl1.ger.corp.intel.com (HELO localhost) ([10.252.20.68]) by orsmga008.jf.intel.com with ESMTP; 12 Nov 2019 12:07:04 -0800 Date: Tue, 12 Nov 2019 22:07:03 +0200 From: Jarkko Sakkinen To: Stefan Berger , linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: question about setting TPM_CHIP_FLAG_IRQ in tpm_tis_core_init Message-ID: <20191112200703.GB11213@linux.intel.com> References: <20191112033637.kxotlhm6mtr5irvd@cantor> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191112033637.kxotlhm6mtr5irvd@cantor> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 11, 2019 at 08:36:37PM -0700, Jerry Snitselaar wrote: > Question about 1ea32c83c699 ("tpm_tis_core: Set TPM_CHIP_FLAG_IRQ > before probing for interrupts"). Doesn't tpm_tis_send set this flag, > and setting it here in tpm_tis_core_init short circuits what > tpm_tis_send was doing before? There is a bug report of an interrupt > storm from a tpm on a t490s laptop with the Fedora 31 kernel (5.3), > and I'm wondering if this change could cause that. Before they got the > warning about interrupts not working, and using polling instead. Looks like it. Stefan? /Jarkko