Received: by 2002:a25:f815:0:0:0:0:0 with SMTP id u21csp163003ybd; Sat, 22 Jun 2019 00:25:31 -0700 (PDT) X-Google-Smtp-Source: APXvYqwkZU5OSDYJA2pL5WEnceh+drmOxa99sa4sS48ebbd4gF0wN+/HCOcWmQV9oV4bAltlKhzD X-Received: by 2002:a63:eb0a:: with SMTP id t10mr3783089pgh.99.1561188331369; Sat, 22 Jun 2019 00:25:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561188331; cv=none; d=google.com; s=arc-20160816; b=ySD9obmg7o/zuWB2jGLnZ/ofNFg3C6jlpIgpcbU2Qpf0LPoEDmOf5UDARBq+ioKvfV ik0ugf4psRQnnzKmx46lMYXe972LeLuePslrwAX6mlJChGOQ22rFARllacCZRU+Jh7RZ rDrN+zO+nenYbjuFT8B1Cjmbuhv4MJkosq1SUDV+uLXGEBDUnRVc7EgjHmw4cbl01O8U kzXpnEQ0LbRb3ZkIlvnubaBb5ZqNgO/UybqjJc9ZFnRUKTDekY4b3D35QsJzFNBntw9O IuJmRSB7YmOpERu3yRLBoF7Y9vWpdpi/Ey1MR7bgZ1Ds58EfZezPhSI7fvBjwBo/vN/5 9eFw== 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=5Bty//ZglWXAPif1P0FdKavwrkI7IMJLolllfNMTlKU=; b=1JarmIjy5/WCgAg22olkOVIF3AQ6Ps8khwZ/ZgaAZK2mQovWRiKeJintXu/VVKCxjA dBD41FKoFx5bfWtIl39F6Qhyhs5vFr+B5XkCqpT8USmGRW1btXu8HicpJFNj8Qrz+Exb pOEcRFr2FafijRL5NiOAIMRtuYNHPu6wZVcbk6OugmQJu86LnCR/lqi8UDhe6OUShSZz r+BYbOqMfowf4na9ZsuPheB17TBAEyvADRi/mQ4w/R+biOnvYCKKrM9uurkNefRuvWQl vb9JSrCV8fnYUHr5feQ9y8yAUXm6D8Av5mhRgC+LmgiIdHTm3ZHEV0goAtPf6Kjsmawr DIww== 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 a17si4916791pjs.98.2019.06.22.00.25.15; Sat, 22 Jun 2019 00:25:31 -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 S1726135AbfFVHXE (ORCPT + 99 others); Sat, 22 Jun 2019 03:23:04 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:57509 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726070AbfFVHXE (ORCPT ); Sat, 22 Jun 2019 03:23:04 -0400 Received: from p5b06daab.dip0.t-ipconnect.de ([91.6.218.171] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1heaL9-0003VY-9L; Sat, 22 Jun 2019 09:21:35 +0200 Date: Sat, 22 Jun 2019 09:21:33 +0200 (CEST) From: Thomas Gleixner To: Ricardo Neri cc: Jacob Pan , Kate Stewart , Peter Zijlstra , Jan Kiszka , Ricardo Neri , Stephane Eranian , Ingo Molnar , Wincy Van , Ashok Raj , x86 , Andi Kleen , Borislav Petkov , "Eric W. Biederman" , "Ravi V. Shankar" , Bjorn Helgaas , Juergen Gross , Tony Luck , Randy Dunlap , LKML , iommu@lists.linux-foundation.org, Philippe Ombredanne Subject: Re: [RFC PATCH v4 20/21] iommu/vt-d: hpet: Reserve an interrupt remampping table entry for watchdog In-Reply-To: <20190621235541.GA25773@ranerica-svr.sc.intel.com> Message-ID: References: <1558660583-28561-21-git-send-email-ricardo.neri-calderon@linux.intel.com> <20190619084316.71ce5477@jacob-builder> <20190621103126.585ca6d3@jacob-builder> <20190621113938.1679f329@jacob-builder> <20190621235541.GA25773@ranerica-svr.sc.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 Fri, 21 Jun 2019, Ricardo Neri wrote: > On Fri, Jun 21, 2019 at 10:05:01PM +0200, Thomas Gleixner wrote: > > On Fri, 21 Jun 2019, Jacob Pan wrote: > > > > > > > I looked at the code again, seems the per cpu HPET code already taken > > > care of HPET MSI management. Why can't we use IR-HPET-MSI chip and > > > domain to allocate and set affinity etc.? > > > Most APIC timer has ARAT not enough per cpu HPET, so per cpu HPET is > > > not used mostly. > > > > Sure, we can use that, but that does not allow to move the affinity from > > NMI context either. Same issue with the IOMMU as with the other hack. > > If I understand Thomas' point correctly, the problem is having to take > lock in NMI context to update the IRTE for the HPET; both as in my hack > and in the generic irq code. The problem is worse when using the generic > irq code as there are several layers and several locks that need to be > handled. It does not matter how many locks are involved. One is enough to wedge the machine. Thanks, tglx