Message ID | 20230619231611.2230-1-xin3.li@intel.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp3315376vqr; Mon, 19 Jun 2023 16:44:27 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7jiKZbrX9VAhc7T1T9uTlMHgxBoJ9aAgx/SZ95cZc0cosXDFl/DcwROA0XZDKqftMdnV7e X-Received: by 2002:a05:6a20:158d:b0:10d:951f:58ba with SMTP id h13-20020a056a20158d00b0010d951f58bamr8270580pzj.52.1687218266945; Mon, 19 Jun 2023 16:44:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1687218266; cv=none; d=google.com; s=arc-20160816; b=LmSWJMIePONdndQ2EVwowinssE0uneUkSgvsrLGmB0mZ8JMbkNmocpVJ8DFfU23KYw RimHL83aVS+DqrQTW7wzT3B/SN6imK/pN/IcGHWCvnNziO5USAcJheYkkmKanIYMTzv1 3SQkSFkZW81pzUovnJEHeKxHOziIkcoVSluUF18uXCi93+V+pTlMEoY9A+RnRyWePbGl ek3P7W1cPeIbCKlK5cMsWJazzAuP/V5rNm/MQLaFZYvtx2gwOzHlGwRSRak+zLhH4UWo POO+Syf9aFtToQska/srn9HD+mxDJDTkSJ3yHrdVIvic9VjIUGULkCKhzfIbL9cJ5GaX UCVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=MS8QTwROCSkexvStZYA4w9fERa7XrSNCoZ7hEcNzzgA=; b=rtTw/Tsgx01DzLk9BlNFl7h2v0YKvH8Gu89SSRmlZqYBdb6TZxYRfG7+BfyE2OoFEX rEXB0lvIaVH5KEgObm6rfZwH0vDTLZ71ep5y4nhV3uc8NTEx8sSEt+oIf7PmKfnKWX7E IanLNJCl0DJnJQgq3xhJTTjfc4TpyjjoTEj4CONLPhh6O87f4I6PU6sAnuKuoonjtSc+ XLK5+PsCW2MzZ0DKGxlvPZJKWhYH50aUFNOT8suNLtm8dcHk9H9JOHqigk5wW5Bza8i0 9+zv4URsFc/4WQKrRY3QnmXQxF9EexOV32+/20/1haYxiaeeybGGfx32cgvV46uxSnUZ 7qig== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Ou8khvC0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l11-20020a170903120b00b001b3cd4f3126si766399plh.439.2023.06.19.16.44.12; Mon, 19 Jun 2023 16:44:26 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=Ou8khvC0; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229678AbjFSXng (ORCPT <rfc822;duw91626@gmail.com> + 99 others); Mon, 19 Jun 2023 19:43:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50636 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229670AbjFSXne (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Mon, 19 Jun 2023 19:43:34 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D504A186; Mon, 19 Jun 2023 16:43:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1687218213; x=1718754213; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=2IydA7aDSW7WAlkvgWIB7B8MuolrT6i4fpDMP7/KzxQ=; b=Ou8khvC0mKcie3XfRCeAvE+vLIfcT9X74jf+zmIyB6SgoyFaa/0JqQzW PMK4fZgKQRXFhNmnT4zgg+xLlMaPx4uGl8+jYzXeESePiQiOrVGhSyTGJ rrmmm6P+jKFurl7nWDceTlhnIbTHAt2ucNuJwFDsHwCAvdiQMxbz8YqIx RUMmozqOhiaCeXXV8YVAr1YV9bn2Lig939B5wWa29lrtQQ7K6BhoYCoxe QdYOI2Aha+KMa32TBdko7GrFzXkFbKqBIypSYQYuOL5Uqe9CLRrUWIEeN xOZ8eZDzKHQy9ccXZspL2b6CRDESUfLkXPjJ1jr++VwsdGHs8t0QWOW+U g==; X-IronPort-AV: E=McAfee;i="6600,9927,10746"; a="340071423" X-IronPort-AV: E=Sophos;i="6.00,255,1681196400"; d="scan'208";a="340071423" Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Jun 2023 16:43:33 -0700 X-IronPort-AV: E=McAfee;i="6600,9927,10746"; a="747789680" X-IronPort-AV: E=Sophos;i="6.00,255,1681196400"; d="scan'208";a="747789680" Received: from unknown (HELO fred..) ([172.25.112.68]) by orsmga001.jf.intel.com with ESMTP; 19 Jun 2023 16:43:31 -0700 From: Xin Li <xin3.li@intel.com> To: linux-kernel@vger.kernel.org, platform-driver-x86@vger.kernel.org, iommu@lists.linux.dev, linux-hyperv@vger.kernel.org, linux-perf-users@vger.kernel.org, x86@kernel.org Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com, steve.wahl@hpe.com, mike.travis@hpe.com, dimitri.sivanich@hpe.com, russ.anderson@hpe.com, dvhart@infradead.org, andy@infradead.org, joro@8bytes.org, suravee.suthikulpanit@amd.com, will@kernel.org, robin.murphy@arm.com, kys@microsoft.com, haiyangz@microsoft.com, wei.liu@kernel.org, decui@microsoft.com, dwmw2@infradead.org, baolu.lu@linux.intel.com, peterz@infradead.org, acme@kernel.org, mark.rutland@arm.com, alexander.shishkin@linux.intel.com, jolsa@kernel.org, namhyung@kernel.org, irogers@google.com, adrian.hunter@intel.com, xin3.li@intel.com, seanjc@google.com, jiangshanlai@gmail.com, jgg@ziepe.ca, yangtiezhu@loongson.cn Subject: [PATCH 0/3] Do IRQ move cleanup with a timer instead of an IPI Date: Mon, 19 Jun 2023 16:16:08 -0700 Message-Id: <20230619231611.2230-1-xin3.li@intel.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1769176581602227097?= X-GMAIL-MSGID: =?utf-8?q?1769176581602227097?= |
Series |
Do IRQ move cleanup with a timer instead of an IPI
|
|
Message
Li, Xin3
June 19, 2023, 11:16 p.m. UTC
No point to waste a vector for cleaning up the leftovers of a moved interrupt. Aside of that this must be the lowest priority of all vectors which makes FRED systems utilizing vectors 0x10-0x1f more complicated than necessary. Schedule a timer instead. Thomas Gleixner (2): x86/vector: Rename send_cleanup_vector() to vector_schedule_cleanup() x86/vector: Replace IRQ_MOVE_CLEANUP_VECTOR with a timer callback Xin Li (1): tools: Get rid of IRQ_MOVE_CLEANUP_VECTOR from tools arch/x86/include/asm/hw_irq.h | 4 +- arch/x86/include/asm/idtentry.h | 1 - arch/x86/include/asm/irq_vectors.h | 7 -- arch/x86/kernel/apic/vector.c | 109 ++++++++++++++---- arch/x86/kernel/idt.c | 1 - arch/x86/platform/uv/uv_irq.c | 2 +- drivers/iommu/amd/iommu.c | 2 +- drivers/iommu/hyperv-iommu.c | 4 +- drivers/iommu/intel/irq_remapping.c | 2 +- tools/arch/x86/include/asm/irq_vectors.h | 7 -- .../beauty/tracepoints/x86_irq_vectors.sh | 2 +- 11 files changed, 92 insertions(+), 49 deletions(-)