Received: by 2002:a05:7412:bbc7:b0:fc:a2b0:25d7 with SMTP id kh7csp621330rdb; Thu, 1 Feb 2024 21:00:10 -0800 (PST) X-Google-Smtp-Source: AGHT+IE7qBTrgiCD0GJ/w+ZtuCpJTE7/Za3vJ3mY/3UiYMe4l7DSA0srDnkSyPpQHj5i9JwqiZdc X-Received: by 2002:a17:903:24f:b0:1d8:ead1:897a with SMTP id j15-20020a170903024f00b001d8ead1897amr7392687plh.64.1706850010331; Thu, 01 Feb 2024 21:00:10 -0800 (PST) ARC-Seal: i=2; a=rsa-sha256; t=1706850010; cv=pass; d=google.com; s=arc-20160816; b=Q1apJrubJeY5BjoMPQPFc3e7zL7NCs+swDr7Lroo791Pip1lWQYIR07M0BYBS//po0 YwpU/2iYz9svFXPUx/78jy2XRfWsLwFclqhCg3tZF1X3eTJz2DrIVxtUJDjySRVL6cU0 m6AUzlxldzOc9LCmq8D8cScQHVL4vqePEMYNOWTG7czW6/73GzhXFHabnmx8upl6Bd7u 9LvVtciba1Q/VCkkH4WiBagkL772saIwulvsTKxw5GtTaoSTT2Dn+KSn5eavC4cpZ4H/ cgmcTLTN7ean+WyRWUoHR/l5RE5wSRh7v1e0mUsIk9HR95FB44eVL73p/l+Zg+X7xmTa gD7A== ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:mime-version:list-unsubscribe :list-subscribe:list-id:precedence:message-id:date:subject:cc:to :from:dkim-signature; bh=V4pusfJ+k5f04/wWYg6r7Wcd1+AiDDOyBg2SYqqfPLw=; fh=cJPFABTE+6+w+byZtgwqP+JIRj1VVDilOLfrWM1lvHo=; b=ENfLxO1eKGvOLDfRNr7dhm9FlTM1puoB5FsL8uJaRuvxrN9unHz7QbtQKtX/P1wSrL bnftK6Oj3RRSHBrb6W/eO211HXpqAfgH9m4P9MtXiS85zQY+qhRVXnsuaM+ZQJ535Wnn yT2Vk6JKPCctxvlEovdMxdFmRNaI0kdhcVZ2IYf+iJlCmIS30ym2pXqcvVEEk0uFJIxy pfm9WN1mQJaGa2d2p/2emEH+s30Lg+VGKqQcqt6CU7uKdLoqM/XLQK3XyiaAw+h6EnsP 9jKCldtatJkOukY5U5JovUup7PHOZqqhzLoirD0r9La8nXQArnHHozS5lv1xPd7ORCQc hlXw==; dara=google.com ARC-Authentication-Results: i=2; mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=J+K0hbCq; arc=pass (i=1 spf=pass spfdomain=intel.com dkim=pass dkdomain=intel.com dmarc=pass fromdomain=intel.com); spf=pass (google.com: domain of linux-kernel+bounces-49204-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-49204-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com X-Forwarded-Encrypted: i=1; AJvYcCVCM62Wd2adlSeWDE1KN2pMlOPLI7Qksr73elQifizcLQZ45tGirIOkgVQ3vG0JfGEdrmZ8mfyRU/+FV/hgVYiTiL1P4A687EZmV3ntgw== Return-Path: Received: from sv.mirrors.kernel.org (sv.mirrors.kernel.org. [2604:1380:45e3:2400::1]) by mx.google.com with ESMTPS id n15-20020a170903110f00b001d8aac2072csi1138760plh.172.2024.02.01.21.00.10 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 01 Feb 2024 21:00:10 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel+bounces-49204-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1; Authentication-Results: mx.google.com; dkim=pass header.i=@intel.com header.s=Intel header.b=J+K0hbCq; arc=pass (i=1 spf=pass spfdomain=intel.com dkim=pass dkdomain=intel.com dmarc=pass fromdomain=intel.com); spf=pass (google.com: domain of linux-kernel+bounces-49204-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) smtp.mailfrom="linux-kernel+bounces-49204-linux.lists.archive=gmail.com@vger.kernel.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: from smtp.subspace.kernel.org (wormhole.subspace.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by sv.mirrors.kernel.org (Postfix) with ESMTPS id 71C25284847 for ; Fri, 2 Feb 2024 04:57:42 +0000 (UTC) Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by smtp.subspace.kernel.org (Postfix) with ESMTP id D86B6FBF2; Fri, 2 Feb 2024 04:57:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b="J+K0hbCq" Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.8]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 0E66FF9C6; Fri, 2 Feb 2024 04:57:25 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=192.198.163.8 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706849849; cv=none; b=F0zcchZgbgz1XSDdOfDTKvE76kYGNu8pnHJALRa08OdFyoncY7ywA3YUOoarGxw3OsIGtp2xgXnMwvo0sZazdEYBVMXuzYxm8YFNqTNjUZ6q1W9CyiqTb4ZWreDBnL2s1oJMxohyoCu0tIp0JUNbaVwIV3Ivuqv+lvMxS+mcEUQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1706849849; c=relaxed/simple; bh=VittVlf1b0271e/PJ8Q1PNQZ9T1Axil9WEjsp2ki1d4=; h=From:To:Cc:Subject:Date:Message-Id:MIME-Version; b=caLYQlGXVaQ4KSGG6VB5cOQApObolGmlO1iZajAg4i91BmGpvSyFQ4g+n30pZcaaP2qojwayxYjJ4cCtbDwNY/RqnfI7icXaYWWFiTq4z+LqZBOJ8/iWIIPoDW6PkGK/1EmiHc7Yj5HBCfdvRZGoG6YcRQE+UCVnVyYWS/hZp/E= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com; spf=pass smtp.mailfrom=intel.com; dkim=pass (2048-bit key) header.d=intel.com header.i=@intel.com header.b=J+K0hbCq; arc=none smtp.client-ip=192.198.163.8 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=intel.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1706849846; x=1738385846; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=VittVlf1b0271e/PJ8Q1PNQZ9T1Axil9WEjsp2ki1d4=; b=J+K0hbCqsCaSKZ/CiEAlocNL45IAnQy8brVvc6ip0pzlCkyRo75DJaxU I4h2VqdA9pVIjOHv8oXJDy6rRT06x6XzjyAGJETrBASdnDR5djfgScn+q I+gGgNL7qWktML9Ly6C1UKHqUqwcsBftBFLXhgaejQIs2Z6TLpoxbTIJw fMXmr2xMX3Tywkc4OhBPsjP6cm/1XoYR24KCio8Y2fpOWM62+8FgBIDeM ZFG2D5bnOzKSPaHm9+/glZJokRi/W8+kV82bnFOZqm/w37hxBCezTYFvu 8A+p0r/Ab8rO9L4lywvRLT0QOixfcWjpVcP/btsxbEmzq1MTatdZ8yFO5 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10971"; a="17615784" X-IronPort-AV: E=Sophos;i="6.05,237,1701158400"; d="scan'208";a="17615784" Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmvoesa102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2024 20:57:25 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10971"; a="912339756" X-IronPort-AV: E=Sophos;i="6.05,237,1701158400"; d="scan'208";a="912339756" Received: from rchatre-ws.ostc.intel.com ([10.54.69.144]) by orsmga004-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2024 20:57:24 -0800 From: Reinette Chatre To: jgg@nvidia.com, yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com, kevin.tian@intel.com, alex.williamson@redhat.com Cc: kvm@vger.kernel.org, dave.jiang@intel.com, ashok.raj@intel.com, reinette.chatre@intel.com, linux-kernel@vger.kernel.org, patches@lists.linux.dev Subject: [PATCH 00/17] vfio/pci: Remove duplicate code and logic from VFIO PCI interrupt management Date: Thu, 1 Feb 2024 20:56:54 -0800 Message-Id: X-Mailer: git-send-email 2.34.1 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hi Everybody, Duplicate VFIO PCI interrupt management code and logic can be found in two areas: 1) the VFIO PCI core (vfio_pci_core.c) directly accesses the VFIO PCI interrupt lock and data to duplicate actions available via the VFIO PCI interrupt management code (vfio_pci_intrs.c), and 2) the INTx and MSI/MSI-X interrupt management code within vfio_pci_intrs.c have duplicate logic. This series addresses (1) and (2) by first containing VFIO PCI interrupt management within the VFIO PCI interrupt management code found in vfio_pci_intrs.c and then refactoring the VFIO PCI interrupt management code (vfio_pci_intrs.c) to share common logic between INTx, MSI, and MSI-X interrupt management. Bulk of the changes result in the same actions as before this series. Two functional changes to highlight: a) "vfio/pci: Consistently acquire mutex for interrupt management" changes vfio_pci_core_disable()->vfio_pci_set_irqs_ioctl() to be called with the igate mutex held. b) "vfio/pci: Preserve per-interrupt contexts" changes MSI/MSI-x interrupt management to preserve per-interrupt contexts across interrupt allocate/free. This work was inspired by (and inherits a few patches from) the IMS [1] enabling work but this work is submitted (and expected to be considered) independent from IMS. Any feedback will be appreciated. Reinette [1] https://lore.kernel.org/lkml/cover.1696609476.git.reinette.chatre@intel.com/ Reinette Chatre (17): vfio/pci: Use unsigned int instead of unsigned vfio/pci: Remove duplicate check from vfio_pci_set_ctx_trigger_single() wrappers vfio/pci: Consistently acquire mutex for interrupt management vfio/pci: Remove duplicate interrupt management from core VFIO PCI vfio/pci: Limit eventfd signaling to interrupt management code vfio/pci: Remove interrupt index interpretation from wrappers vfio/pci: Preserve per-interrupt contexts vfio/pci: Extract MSI/MSI-X specific code from common flow vfio/pci: Converge similar code flows vfio/pci: Extract INTx specific code from vfio_intx_set_signal() vfio/pci: Perform MSI/MSI-X interrupt management via callbacks vfio/pci: Remove msi term from generic code vfio/pci: Remove vfio_intx_set_signal() vfio/pci: Add utility to trigger INTx eventfd knowing interrupt context vfio/pci: Let enable and disable of interrupt types use same signature vfio/pci: Move vfio_msi_disable() to be with other MSI/MSI-X management code vfio/pci: Remove duplicate interrupt management flow drivers/vfio/pci/vfio_pci_core.c | 49 ++- drivers/vfio/pci/vfio_pci_intrs.c | 510 ++++++++++++++++++------------ 2 files changed, 318 insertions(+), 241 deletions(-) base-commit: 41bccc98fb7931d63d03f326a746ac4d429c1dd3 -- 2.34.1