public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@linux.intel.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
	Jesse Barnes <jbarnes@virtuousgeek.org>, Martin Mares <mj@ucw.cz>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org,
	the arch/x86 maintainers <x86@kernel.org>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-arch@vger.kernel.org
Subject: Re: RFC: x86: cap iomem_resource to addressable physical memory
Date: Thu, 11 Jun 2009 13:46:52 -0700	[thread overview]
Message-ID: <4A316D3C.7080403@linux.intel.com> (raw)
In-Reply-To: <86802c440906111343g513a2ceau1e2bfdf14c295b2d@mail.gmail.com>

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.

	-hpa

  reply	other threads:[~2009-06-11 20:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-10  1:32 RFC: x86: cap iomem_resource to addressable physical memory H. Peter Anvin
2009-06-10  1:32 ` H. Peter Anvin
2009-06-11 19:17 ` Jesse Barnes
2009-06-11 19:17   ` Jesse Barnes
2009-06-11 20:43 ` Yinghai Lu
2009-06-11 20:46   ` H. Peter Anvin [this message]
2009-06-11 20:46     ` H. Peter Anvin
2009-06-21  6:42     ` Pavel Machek
2009-06-21  6:42       ` Pavel Machek
2009-06-21  7:40       ` H. Peter Anvin
2009-06-21 20:55         ` Pavel Machek
2009-06-21 20:55           ` Pavel Machek
2009-06-22  7:54           ` H. Peter Anvin
2009-06-22  7:54             ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A316D3C.7080403@linux.intel.com \
    --to=hpa@linux.intel.com \
    --cc=dwmw2@infradead.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=mj@ucw.cz \
    --cc=x86@kernel.org \
    --cc=yhlu.kernel@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox