Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4048694ybl; Mon, 12 Aug 2019 10:28:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqwHXm2YSTrRpaHtJEs6dPql/oXR09y405NWXNHzhY6gbr637zCvyphw7VOfdB0Up3JfBE4l X-Received: by 2002:a63:a35e:: with SMTP id v30mr30017846pgn.129.1565630916632; Mon, 12 Aug 2019 10:28:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565630916; cv=none; d=google.com; s=arc-20160816; b=bsbP+6fX8nI43LiuEDgejzDLkdToKskmv3qPTIqC5P+BNl1ELpGalr4w0wpnRchjau ODWqyARmkru14nkvExv5NyUpacIR5pJkQSnCUpuPH6P0veSaML4fb1sqrkTMMrijZNr0 +9o93z15M82JvAA17I6wqx+UTKPorwFnjAJiJojUQTqsXjqu9w8xEpxGqqpTaT6rYuC3 DBtxm/weazRPddJpInohNNcQ5vS1RBDU6KeUkuIFl9aK2Xmt7dYq9AmtOAMIC9mT1oyo aff8j+lgX9UGRLRHUvFWt6QPinUkL6rzMtni+5E0v/KXHkJ983rBx1acgADIyIjANuYz 0Y2Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=OTee53JXozoX39DV/R9lbL9JwDdm43TY1z/FCe8TxM8=; b=Uzi9PKR4tGGXfNReIQWTNrvdUCe8MBpt7n8hA2uFCmEYu4nn1oShouBa90g1+C134q XLhrtIOMBdngpuhl2cNqCmoCL4jxAbm5RGawim5J7I4R433o0qeAOWAUIF0LlvhCFSpO R+WI+drNoGtZOB/ShtHR/U3vUdYEO5CpJzwbKJXyJLVyxUuzDJaPx/vUKTysG/0J4kKg ehNPIc11hQVhRvKPBHm5sKB7ZocNGNslgQ59LEePKp6izbsZA0D2IPk/Ca/jNVRZ5iq4 t72a0XG7WCojtEGf/YBkYhgFDJgVKg1bGmhuWHm3WzLZ4AtZaMB4xYZj6mluk867pq/S kDpA== 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 e10si57170381pls.163.2019.08.12.10.28.19; Mon, 12 Aug 2019 10:28:36 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726982AbfHLR0v (ORCPT + 99 others); Mon, 12 Aug 2019 13:26:51 -0400 Received: from mga09.intel.com ([134.134.136.24]:24983 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726457AbfHLR0v (ORCPT ); Mon, 12 Aug 2019 13:26:51 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Aug 2019 10:26:50 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,378,1559545200"; d="scan'208";a="259864026" Received: from megha-z97x-ud7-th.sc.intel.com ([143.183.85.162]) by orsmga001.jf.intel.com with ESMTP; 12 Aug 2019 10:26:50 -0700 Message-ID: <1565632084.7042.13.camel@intel.com> Subject: Re: [RFC V1 RESEND 2/6] PCI/MSI: Dynamic allocation of MSI-X vectors by group From: Megha Dey To: Marc Zyngier , Thomas Gleixner Cc: bhelgaas@google.com, linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org, ashok.raj@intel.com, jacob.jun.pan@linux.intel.com Date: Mon, 12 Aug 2019 10:48:04 -0700 In-Reply-To: <48a44ffc-4b5b-5eef-73de-020f1710c41e@arm.com> References: <1561162778-12669-1-git-send-email-megha.dey@linux.intel.com> <1561162778-12669-3-git-send-email-megha.dey@linux.intel.com> <1565118316.2401.112.camel@intel.com> <48a44ffc-4b5b-5eef-73de-020f1710c41e@arm.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.18.5.2-0ubuntu3.2 Mime-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2019-08-07 at 15:18 +0100, Marc Zyngier wrote: > On 07/08/2019 14:56, Thomas Gleixner wrote: > > > > Megha, > > > > On Tue, 6 Aug 2019, Megha Dey wrote: > > > > > > On Sat, 2019-06-29 at 09:59 +0200, Thomas Gleixner wrote: > > > > > > > > On Fri, 21 Jun 2019, Megha Dey wrote: > > > Totally agreed. The request to add a dynamic MSI-X infrastructure > > > came > > > from some driver teams internally and currently they do not have > > > bandwidth to come up with relevant test cases. > > Hahahaha. > > > > > > > > But we hope that this patch set could serve as a precursor to the > > > interrupt message store (IMS) patch set, and we can use this > > > patch set > > > as the baseline for the IMS patches. > > If IMS needs the same functionality, then we need to think about it > > slightly differently because IMS is not necessarily tied to PCI. > >   > > IMS has some similarity to the ARM GIC ITS stuff IIRC, which > > already > > provides these things outside of PCI. Marc? > Indeed. We have MSI-like functionality almost everywhere, and make > heavy > use of the generic MSI framework. Platform-MSI is probably the most > generic example we have (it's the Far West transposed to MSIs). > Ok I will have a look at the platform-msi code. > > > > We probably need some generic infrastructure for this so PCI and > > everything > > else can use it. > Indeed. Overall, I'd like the concept of MSI on whatever bus to have > one > single behaviour across the board, as long as it makes sense for that > bus (nobody needs another PCI MultiMSI, for example). Yeah, agreed. > > Thanks, > > M.