Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp813258ybi; Fri, 21 Jun 2019 08:35:10 -0700 (PDT) X-Google-Smtp-Source: APXvYqwFppDXleCwK5baRYRUyl138jKhWbW6PLDBurAPfB0hZkp3KKiVnWalQ62DmBRcdXgYRbav X-Received: by 2002:a17:902:1004:: with SMTP id b4mr7600812pla.325.1561131310654; Fri, 21 Jun 2019 08:35:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1561131310; cv=none; d=google.com; s=arc-20160816; b=XZsKkVZwWsKSrVN5F8tz85zh3NytS9je71Zrpxxsjm/bZ7ZjB8ohUsi5oYzkzCKkaJ Pt8fXwFIhQoG9pwIIZ9en2ntHp9TkHIsraBMRsu9fFkStxwSN2l+bqWghN4zGUHFTGdS Rjf4McJllni2rA4mo9jrYBgXhJHv9s4dJ16Pcnl4vonNSpgCdx5h47a8MzK58dD6k3/Q 6zYut9MfdXpIAFBCM7xqgBJRAU4KDxpScHSS/pPBvQ6d7hzb2ROhBbDMfl25dUXGHvcW 1Rc3hfGzu7FoGbu41vGeM/ffxkLd3jR+RvcMuuSxpV9NGVWaFvSvs4pdjp3uA9XyjdNb Lj9A== 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=YACyNq5o5yEN5QNKo/x8cD0UhFn8oE17PWLWWPPESzY=; b=nUXzwT95bkuKcRp1lHBPfFRqIJD1QEAkXINGSCiFjCzlZzNmFygS+f5wB9/CDq+BO2 vPW39DpM+V6Gfs6k/WiurJO5WRvBKwZkBEOATIE7VxGAsDsRWKcXo7fWsG7fli1i1uwL pFA8UaZTGkh6UTCUhBpujGqyLA/dUSYVnDgLvJKHtxmjmCrPk2XlGpG5DtI6w1JDLnf5 jxicBMTWXmjDu44IGPMYmGxYc9sTWcMS69B1fp59Y5xLY80opGu1EQ4/4BkLCyi8mnKg Sc9DzktsHJ7Gj8aUA7eE42CtaisczyFAv4f1XQyLduNArMFeBkUVz5D1b4HC8Ol8hHa/ iBdQ== 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 y70si1464683pfg.172.2019.06.21.08.34.54; Fri, 21 Jun 2019 08:35:10 -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 S1726137AbfFUPeq (ORCPT + 99 others); Fri, 21 Jun 2019 11:34:46 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:55295 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726045AbfFUPeq (ORCPT ); Fri, 21 Jun 2019 11:34:46 -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 1heLXd-00065k-Gq; Fri, 21 Jun 2019 17:33:29 +0200 Date: Fri, 21 Jun 2019 17:33:28 +0200 (CEST) From: Thomas Gleixner To: Jacob Pan cc: Stephane Eranian , Kate Stewart , Peter Zijlstra , Jan Kiszka , Ricardo Neri , Ingo Molnar , Wincy Van , Ashok Raj , x86 , Andi Kleen , Borislav Petkov , "Eric W. Biederman" , "Ravi V. Shankar" , Ricardo Neri , 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: <20190619084316.71ce5477@jacob-builder> Message-ID: References: <1558660583-28561-1-git-send-email-ricardo.neri-calderon@linux.intel.com> <1558660583-28561-21-git-send-email-ricardo.neri-calderon@linux.intel.com> <20190619084316.71ce5477@jacob-builder> 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 Wed, 19 Jun 2019, Jacob Pan wrote: > On Tue, 18 Jun 2019 01:08:06 +0200 (CEST) > Thomas Gleixner wrote: > > > > Unless this problem is not solved and I doubt it can be solved after > > talking to IOMMU people and studying manuals, > > I agree. modify irte might be done with cmpxchg_double() but the queued > invalidation interface for IRTE cache flush is shared with DMA and > requires holding a spinlock for enque descriptors, QI tail update etc. > > Also, reserving & manipulating IRTE slot for hpet via backdoor might not > be needed if the HPET PCI BDF (found in ACPI) can be utilized. But it > might need more work to add a fake PCI device for HPET. What would PCI/BDF solve? Thanks, tglx