lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-Id: <201301111536.14799.arnd@arndb.de> Date: Fri, 11 Jan 2013 15:36:14 +0000 From: Arnd Bergmann <arnd@...db.de> To: Thierry Reding <thierry.reding@...onic-design.de> Cc: Stephen Warren <swarren@...dotorg.org>, linux-tegra@...r.kernel.org, Grant Likely <grant.likely@...retlab.ca>, Rob Herring <rob.herring@...xeda.com>, Russell King <linux@....linux.org.uk>, Bjorn Helgaas <bhelgaas@...gle.com>, Andrew Murray <andrew.murray@....com>, Jason Gunthorpe <jgunthorpe@...idianresearch.com>, Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>, devicetree-discuss@...ts.ozlabs.org, linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-pci@...r.kernel.org Subject: Re: [PATCH 10/14] PCI: tegra: Move PCIe driver to drivers/pci/host On Friday 11 January 2013, Thierry Reding wrote: > Right, it'll need #ifdefs around the arch_{setup,teardown}_msi_irq(). Or > select PCI_MSI unconditionally. Once this is merged I was going to post > a patch that enables PCI_MSI in tegra_defconfig anyway. But it might be > better to keep it optional anyway since the remainder of the code copes > with it properly. > Actually, we need something better than that. You cannot define arch_setup_msi_irq in a tegra specific pci host driver, because that will seriously mess up other platforms in multiplatform configurations by giving a link error when they also define this function, or with a run-time error when they don't support it. I think what we should do here is fix it the right way by adding a pci host specific callback rather than an architecture specific callback in drivers/pci/msi.c. There is already a default version of arch_setup_msi_irqs (with s), and we can probably do the same for arch_setup_msi_irq (without s) to fall back to the arch version for most architectures. Most architectures (at least powerpc, sparc, ia64 and x86) already multiplex the msi handlers internally, but ARM does not because there is only one implementation (iop33x) at the moment. We can add a generix multiplex and then move architectures over to use it. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists