[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20071227060948.69a852a5@laptopd505.fenrus.org>
Date: Thu, 27 Dec 2007 06:09:48 -0800
From: Arjan van de Ven <arjan@...radead.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Loic Prylli <loic@...i.com>, linux-kernel@...r.kernel.org,
gregkh@...e.de, linux-pci@...ey.karlin.mff.cuni.cz,
Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [patch] Make MMCONFIG space (extended PCI config space) a
driver opt-in issue
On Thu, 27 Dec 2007 06:46:22 -0500
Jeff Garzik <jeff@...zik.org> wrote:
> Linus Torvalds wrote:
> > Well, the *current* behaviour as far as setup is concerned is
> > unacceptable. But yes, longer term, we should be able to just have
> > quirk entries for saying "enable mmconfig because I know it's
> > safe", except we should not enable them until after the core PCI
> > probing has completed.
>
>
> IMO that should be an arch decision, buried somewhere in arch/x86.
>
> If other arches implement extended config space sanely -- and
> possibly via some arch-specific means that is /not/ mmconfig -- then
> they should be able to make an arch decision that extended PCI config
> space accesses Just Work(tm).
>
> For such arches, pci_enable_ext_cfg_space(pdev) would be a no-op,
> always returning success.
>
both the first and the second patch already have this behavior.
--
If you want to reach me at my work email, use arjan@...ux.intel.com
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
--
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