Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756121AbZAMCsK (ORCPT ); Mon, 12 Jan 2009 21:48:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751189AbZAMCrz (ORCPT ); Mon, 12 Jan 2009 21:47:55 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:59221 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750948AbZAMCry (ORCPT ); Mon, 12 Jan 2009 21:47:54 -0500 Message-ID: <496C00CD.3070302@jp.fujitsu.com> Date: Tue, 13 Jan 2009 11:47:41 +0900 From: Kenji Kaneshige User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: "Rafael J. Wysocki" CC: Jesse Barnes , Linux PCI , LKML Subject: Re: [PATCH 5/8] PCI PCIe portdrv: Fix allocation of interrupts References: <200901042346.42723.rjw@sisk.pl> <200901082145.39429.rjw@sisk.pl> <200901091533.44460.jbarnes@virtuousgeek.org> <200901100038.56748.rjw@sisk.pl> In-Reply-To: <200901100038.56748.rjw@sisk.pl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2419 Lines: 49 Rafael J. Wysocki wrote: > On Saturday 10 January 2009, Jesse Barnes wrote: >> On Thursday, January 8, 2009 12:45 pm Rafael J. Wysocki wrote: >>> On Thursday 08 January 2009, Rafael J. Wysocki wrote: >>>> On Thursday 08 January 2009, Kenji Kaneshige wrote: >>>>> Rafael J. Wysocki wrote: >>>>>> On Thursday 08 January 2009, Kenji Kaneshige wrote: >>>>>>> Rafael J. Wysocki wrote: >>>>>>>> From: Rafael J. Wysocki >>>>>>>> >>>>>>>> If MSI-X interrupt mode is used by the PCI Express port driver, too >>>>>>>> many vectors are allocated and it is not ensured that the right >>>>>>>> vectors will be used for various services. Namely, the PCI Express >>>>>>>> specification states that both PCI Express native PME and PCI >>>>>>>> Express hotplug will always use the same MSI or MSI-X message for >>>>>>>> signalling interrupts, which implies that the same vector will be >>>>>>>> used by both of them. Also, the VC service does not use interrupts >>>>>>>> at all. Moreover, is not clear which of the vectors allocated by >>>>>>>> pci_enable_msix() will be used for PME and hotplug and which of >>>>>>>> them will be used for AER if all of these services are configured. >>>>>>>> >>>>>>>> For these reasons, rework the allocation of interrupts for PCI >>>>>>>> Express ports so that at most two vectors are allocated and ensure >>>>>>>> that the right vector will be used for the right purpose. >>> Appended is a cleaned-up version of the patch that also contains comments >>> with references to the appropriate sections of the PCI Express spec. >> We'll need testing here in any case; I'll have to re-read the specs carefully >> to see if we can really rely on the vector numbers you have here (at first >> glance Kenji-san's approach seems more robust). > > It has a catch too. Namely, is there any warranty that we'll get the same > vectors when the second pci_enable_msix() is called and that they will be in > the same order? > In my understanding, the following description of Interrupt Message Number in the PCI Express spec explains this. "[...] For a given MSI-X implementation, the entry must remain constant. [...]" Thanks, Kenji Kaneshige -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/