Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935247AbaKNMNa (ORCPT ); Fri, 14 Nov 2014 07:13:30 -0500 Received: from www.linutronix.de ([62.245.132.108]:52525 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933506AbaKNMN3 (ORCPT ); Fri, 14 Nov 2014 07:13:29 -0500 Date: Fri, 14 Nov 2014 13:13:03 +0100 (CET) From: Thomas Gleixner To: Jiang Liu cc: Yijing Wang , Marc Zyngier , Bjorn Helgaas , Ingo Molnar , "grant.likely@linaro.org" , Yingjoe Chen , Borislav Petkov , "H. Peter Anvin" , Matthias Brugger , Tony Luck , "linux-kernel@vger.kernel.org" , "linux-pci@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [Patch V1 0/6] Refine generic/PCI MSI irqodmian interfaces In-Reply-To: <54655D44.1070703@linux.intel.com> Message-ID: References: <1415879029-20098-1-git-send-email-jiang.liu@linux.intel.com> <54651BE2.9080008@arm.com> <54654C10.2040102@linux.intel.com> <54655632.2040209@huawei.com> <54655D44.1070703@linux.intel.com> User-Agent: Alpine 2.11 (DEB 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 14 Nov 2014, Jiang Liu wrote: > On 2014/11/14 9:31, Thomas Gleixner wrote: > > On Fri, 14 Nov 2014, Yijing Wang wrote: > > > > Could you please use a mail client which does proper line wraps or > > configure yours to do so? > > > >> Associate the irq domain and PCI bus is not necessary, because all > >> PCI buses under same host bridge always share same MSI chip/irq > >> domain, we only need associate them and pci host bridge. > >> > >> I'm refactoring the pci_host_bridge, make it be a generic one, rip > >> out of the pci root bus creation, so we could put the irq domain and > >> pci domain etc.. in it. Finally, we could eliminate lots platform > >> arch functions. I will post it out within one week. > > > > That's a completely orthogonal problem. From the MSI/interrupt > > handling POV it does not matter at all where that information is > > stored. All we care about is that it is retrievable via the (pci) > > device which tries to setup MSI[X]. > > > > So we can store/retrieve it via generic functions into/from whatever > > is available right now. If the irq side has generic interfaces to do > > so then this wont conflict with your decisions to change the final > > storage point because all it takes is to tweak the storage/retrieve > > functions. > > > > So all we need at the moment is an agreed on way to store/retrieve > > that information which is based on the current shared infrastructure, > > aka. Linus tree. If we can utilize that you are completely free to > > change the association mechanism underneath. > Hi Thomas, > So we need something like: > struct msi_chip *pci_get_msi_chip(struct pci_dev *); > or: > struct irq_domain *pci_get_msi_domain(struct pci_dev *); > > BTW, there's a conflict when merging tip/irq/irqdomain into > tip/x86/apic. It's my first time to deal with merging conflicts, > what's the preferred way? Is it working like this? > 1) I merge the two branch > 2) I rebase my x86 irqdomain patch sets and send them to you > 3) You merge the two branch and apply my patch set. When we have the generic parts sorted out, i'll make the irq/irqdomain branch official and immutable and then merge it into x86/apic fix the conflicts and add the x86 specific stuff on top. Thanks, tglx -- 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/