From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: RFC: x86: cap iomem_resource to addressable physical memory Date: Sun, 21 Jun 2009 08:42:01 +0200 Message-ID: <20090621064201.GD1656@ucw.cz> References: <4A2F0D45.2040602@linux.intel.com> <86802c440906111343g513a2ceau1e2bfdf14c295b2d@mail.gmail.com> <4A316D3C.7080403@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4A316D3C.7080403@linux.intel.com> Sender: linux-pci-owner@vger.kernel.org To: "H. Peter Anvin" Cc: Yinghai Lu , Matthew Wilcox , Jesse Barnes , Martin Mares , LKML , linux-pci@vger.kernel.org, the arch/x86 maintainers , David Woodhouse , linux-arch@vger.kernel.org List-Id: linux-arch.vger.kernel.org On Thu 2009-06-11 13:46:52, H. Peter Anvin wrote: > Yinghai Lu wrote: > > > > do we need do that on every cpu? > > > > looks like we could do that in identify_boot_cpu. > > > > What if the CPUs are heterogenous? It's obviously a suboptimal > situation, but it doesn't seem like something we can rely on. Is it ok if that changes during runtime? What if someone hotplugs heterogenous cpu? I'd say basing it on boot cpu seems simplest. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html