Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp340918yba; Mon, 1 Apr 2019 07:29:17 -0700 (PDT) X-Google-Smtp-Source: APXvYqze84mCkxoASibgctc4nHwEJFqTGyGVCTEL89iMIwuf5qtdUkDujkzlcF/NEfxEj+1GtXkE X-Received: by 2002:a63:8548:: with SMTP id u69mr60613690pgd.85.1554128957724; Mon, 01 Apr 2019 07:29:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554128957; cv=none; d=google.com; s=arc-20160816; b=dL62HEg+brjWVOXPnwC/iJ/3myMBregYF60W7EB4FtOpyfA8OIQSi3B96I8uZJ6V0G WByhaLEevbU9lY0Pdhr9foaEVX+PFomLHuu7ceLuO4I91/MV3D21lOJygR5YUu+H7bHg 9fu8HrlsPgtMlNyKz6oUBNemV5aBt7VzSIEVw7IiC/g1vzObcraJ6uOhNqa4YAlUhy8g jIylJaLfybON3lgS8Nn0qNeXEp2Uf4aOIrLgu3WwQkTGCZtGYINPNRtfNIqq1ztWB3UQ U6swDEwKo+7jux5vUSMZ47ydEOMXCrDHFiWrEtrHrrJV3fyay5EeFKkf7AZMLz2vSb3z zQbQ== 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 :user-agent:date:message-id:subject:from:cc:to; bh=E1NsFvfKqZBXoG1md1kWSzXpkNG6fAA0oDNQ7KhfWFo=; b=ZlLyI5mou8WO4koAelhOeJXCPZDXcGg4PRhmHsy4KwwaV1lEJZ+6Jzb6PKjNyhrvNR K4rpOVcVwwEWYMHGdVHnBkSyfZnVkTfsOSucKd9chFLq9GVYVdYc6dI2B17NsSnBmuMY gP7jg6SMcmATsXUuvdtVMIcw/L70KD7DAPa0cKgBMJc+mODihsJkMlh5MBkQGX8unx2P Q7jbEDF5+PN4omDp7vDr7UsQddiagk2rEOTnzpqOZd1uItZ06O3BoCYtGdiX7qlP6kbj ik8SfLDBIQ2hJsC6jaRMMzMLOhjo/dIVdmp1aiy1RDmTp99QK04acWqjbI3LWGxyMLJ8 5Y2Q== 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 d23si9168730pfd.93.2019.04.01.07.29.02; Mon, 01 Apr 2019 07:29:17 -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 S1728109AbfDAO2X (ORCPT + 99 others); Mon, 1 Apr 2019 10:28:23 -0400 Received: from szxga07-in.huawei.com ([45.249.212.35]:45236 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727415AbfDAO2X (ORCPT ); Mon, 1 Apr 2019 10:28:23 -0400 Received: from DGGEMS401-HUB.china.huawei.com (unknown [10.3.19.201]) by Forcepoint Email with ESMTP id BE7AC32D2DE989B1C6DE; Mon, 1 Apr 2019 22:28:18 +0800 (CST) Received: from [127.0.0.1] (10.177.31.55) by DGGEMS401-HUB.china.huawei.com (10.3.19.201) with Microsoft SMTP Server id 14.3.408.0; Mon, 1 Apr 2019 21:55:52 +0800 To: CC: Marc Zyngier , Thomas Gleixner , Jason Cooper , wanghaibin 00208455 From: Heyi Guo Subject: MSI number limit for PCI hotplug under PCI bridge on ARM platform Message-ID: <327ba551-2cbd-08bb-d4c1-107c3ff7d45d@huawei.com> Date: Mon, 1 Apr 2019 21:55:52 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.177.31.55] Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi folks, In current kernel implementation for ARM platform, all devices under one PCI bridge share a same device ID and the total number of MSI interrupts is fixed at the first time any child device is allocating MSI. However, this may cause failure of allocating MSI if the system supports device hot-plug under the PCI bridge, which is possible for ARM virtual machine with generic pcie-to-pci-bridge and kernel config HOTPLUG_PCI_SHPC enabled. Does it make sense to add support for the above scenario? If it does, any suggestion for how to do that? Thanks, Heyi