From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"x86@kernel.org" <x86@kernel.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Jan Beulich <JBeulich@novell.com>
Subject: Re: [PATCH] x86/mm/init: respect memblock reserved regions when destroying mappings
Date: Wed, 02 Feb 2011 12:15:21 -0800 [thread overview]
Message-ID: <4D49BB59.8000303@goop.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1101311514580.7277@kaball-desktop>
On 01/31/2011 07:18 AM, Stefano Stabellini wrote:
> x86/mm/init: respect memblock reserved regions when destroying mappings
>
> In init_memory_mapping we are destroying all the mappings between
> _brk_end and _end, no matter if some memory areas in that range have
> been reserved using memblock_x86_reserve_range.
What's reserving things in that range? How do they get addresses
there? I would have thought they should all be brk-allocated?
> Besides if _end is not pmd aligned we might destroy the
> mappings for valid memory between _end and the following pmd.
Yes, that could be messy.
J
> In order to avoid this problem, before clearing any pmds we check if the
> corresponding memory area has been reserved and we only destroy the
> mapping if it hasn't.
>
> We found this problem because under Xen we have a valid mapping at _end,
> and if _end is not pmd aligned the current code destroys the initial
> part of it.
>
> In practice this fix does not have any impact on native.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
>
> diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
> index 947f42a..66637bd 100644
> --- a/arch/x86/mm/init.c
> +++ b/arch/x86/mm/init.c
> @@ -283,6 +283,8 @@ unsigned long __init_refok init_memory_mapping(unsigned long start,
> if (!after_bootmem && !start) {
> pud_t *pud;
> pmd_t *pmd;
> + unsigned long addr;
> + u64 size, memblock_addr;
>
> mmu_cr4_features = read_cr4();
>
> @@ -291,11 +293,18 @@ unsigned long __init_refok init_memory_mapping(unsigned long start,
> * located on different 2M pages. cleanup_highmap(), however,
> * can only consider _end when it runs, so destroy any
> * mappings beyond _brk_end here.
> + * Respect memblock reserved regions.
> */
> pud = pud_offset(pgd_offset_k(_brk_end), _brk_end);
> pmd = pmd_offset(pud, _brk_end - 1);
> - while (++pmd <= pmd_offset(pud, (unsigned long)_end - 1))
> - pmd_clear(pmd);
> + addr = (_brk_end + PMD_SIZE - 1) & PMD_MASK;
> + while (++pmd <= pmd_offset(pud, (unsigned long)_end - 1)) {
> + memblock_addr = memblock_x86_find_in_range_size(__pa(addr),
> + &size, PMD_SIZE);
> + if (memblock_addr == (u64) __pa(addr) && size >= PMD_SIZE)
> + pmd_clear(pmd);
> + addr += PMD_SIZE;
> + }
> }
> #endif
> __flush_tlb_all();
next prev parent reply other threads:[~2011-02-02 20:15 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-31 15:18 [PATCH] x86/mm/init: respect memblock reserved regions when destroying mappings Stefano Stabellini
2011-02-02 20:15 ` Jeremy Fitzhardinge [this message]
2011-02-03 5:05 ` H. Peter Anvin
2011-02-03 11:25 ` Stefano Stabellini
2011-02-03 17:02 ` H. Peter Anvin
2011-02-04 11:35 ` Stefano Stabellini
2011-02-05 1:18 ` Jeremy Fitzhardinge
2011-02-06 7:02 ` Yinghai Lu
2011-02-06 7:30 ` H. Peter Anvin
2011-02-06 17:49 ` Yinghai Lu
2011-02-06 19:24 ` Yinghai Lu
2011-02-07 16:50 ` Stefano Stabellini
2011-02-07 18:04 ` Yinghai Lu
2011-02-07 18:58 ` Stefano Stabellini
2011-02-07 19:00 ` Yinghai Lu
2011-02-07 19:18 ` Yinghai Lu
2011-02-07 21:56 ` Jeremy Fitzhardinge
2011-02-08 3:12 ` Yinghai Lu
2011-02-08 4:56 ` Jeremy Fitzhardinge
2011-02-08 5:09 ` Yinghai Lu
2011-02-08 14:55 ` Konrad Rzeszutek Wilk
2011-02-08 19:24 ` Jeremy Fitzhardinge
2011-02-08 20:26 ` Stefano Stabellini
2011-02-08 19:34 ` H. Peter Anvin
2011-02-10 23:48 ` Jeremy Fitzhardinge
2011-02-10 23:57 ` Yinghai Lu
2011-02-11 0:35 ` H. Peter Anvin
2011-02-11 0:54 ` Yinghai Lu
2011-02-14 16:26 ` Konrad Rzeszutek Wilk
2011-02-14 17:55 ` Yinghai Lu
2011-02-14 17:58 ` Stefano Stabellini
2011-02-14 18:09 ` Yinghai Lu
2011-02-14 20:02 ` H. Peter Anvin
2011-02-16 17:36 ` Stefano Stabellini
2011-02-07 19:00 ` Stefano Stabellini
2011-02-08 5:16 ` Yinghai Lu
2011-02-08 14:03 ` Stefano Stabellini
2011-02-08 16:04 ` Yinghai Lu
2011-02-07 16:02 ` Stefano Stabellini
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=4D49BB59.8000303@goop.org \
--to=jeremy@goop.org \
--cc=JBeulich@novell.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.