From: Yinghai Lu <yinghai@kernel.org>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: another pagetable initialization crash on xen
Date: Wed, 30 Mar 2011 10:58:05 -0700 [thread overview]
Message-ID: <4D936F2D.4000902@kernel.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103301748380.16492@kaball-desktop>
On 03/30/2011 09:59 AM, Stefano Stabellini wrote:
> On Wed, 30 Mar 2011, Stefano Stabellini wrote:
>> I have another unrelated question: init_memory_mapping is called on the
>> range 0 - max_low_pfn, but that range usually includes a reserved region
>> below the first MB. On one machine of mine the IOAPIC mmio region falls
>> in that memory range therefore we are mapping the IOAPIC mmio region in
>> init_memory_mapping without going through the fixmap as we should.
>> This is causing problems on Xen, but I guess it could theoretically
>> cause problems on other platforms as well. Should we avoid reserved
>> memory regions below the first MB from the initial memory mappings?
>
> Sorry I mixed up frame numbers with physical addresses, so the IOAPIC
> mmio region is actually at 0xfec00000 where it should be but it gets
> mapped during the initial memory mapping (range 0 - 0x100000000).
> Is that supposed to happen? Shouldn't it go through the fixmap?
io apic addr is going through fixmap.
initial_memory_mapping will map to [0, max_mem_under_4g).
max_mem_under_4g is from E820 table searching.
later it will map [4g, max_mem_above_4g).
We do not map mmio gap between [max_mem_under_4g,4g)
Thanks
Yinghai
next prev parent reply other threads:[~2011-03-30 17:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-28 17:26 another pagetable initialization crash on xen Stefano Stabellini
2011-03-28 19:04 ` Stefano Stabellini
2011-03-29 17:25 ` Stefano Stabellini
2011-03-29 18:15 ` Yinghai Lu
2011-03-30 16:26 ` Stefano Stabellini
2011-03-30 16:59 ` Stefano Stabellini
2011-03-30 17:58 ` Yinghai Lu [this message]
2011-04-05 13:47 ` Stefano Stabellini
2011-03-30 16:05 ` Konrad Rzeszutek Wilk
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=4D936F2D.4000902@kernel.org \
--to=yinghai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.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