From: Yinghai Lu <yinghai@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Tejun Heo <tj@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] x86,mm,64bit: Round up memory boundary for init_memory_mapping_high()
Date: Fri, 25 Feb 2011 12:22:15 -0800 [thread overview]
Message-ID: <4D680F77.5060107@kernel.org> (raw)
In-Reply-To: <20110225100336.GA26608@elte.hu>
On 02/25/2011 02:03 AM, Ingo Molnar wrote:
>
> * Yinghai Lu <yinghai@kernel.org> wrote:
>
>> init_memory_mapping_active_regions(unsigned long start, unsigned long end)
>> {
>> struct mapping_work_data data;
>> + int use_gbpages;
>> +
>> + /* see init_memory_mapping() for the setting */
>> +#if defined(CONFIG_DEBUG_PAGEALLOC) || defined(CONFIG_KMEMCHECK)
>> + use_gbpages = 0;
>> +#else
>> + use_gbpages = direct_gbpages;
>> +#endif
>
> Sigh. You should *never* ever even think about writing such code. It only results in
> crap, and in crap duplicated elsewhere as well:
>
> if defined(CONFIG_DEBUG_PAGEALLOC) || defined(CONFIG_KMEMCHECK)
> /*
> * For CONFIG_DEBUG_PAGEALLOC, identity mapping will use small pages.
> * This will simplify cpa(), which otherwise needs to support splitting
> * large pages into small in interrupt context, etc.
> */
> use_pse = use_gbpages = 0;
> #else
> use_pse = cpu_has_pse;
> use_gbpages = direct_gbpages;
> #endif
sorry, actually i copied from there.
or i could add max_map_unit_size variable?
Thanks
Yinghai
next prev parent reply other threads:[~2011-02-25 20:23 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-23 17:19 questions about init_memory_mapping_high() Tejun Heo
2011-02-23 20:24 ` Yinghai Lu
2011-02-23 20:46 ` Tejun Heo
2011-02-23 20:51 ` Yinghai Lu
2011-02-23 21:03 ` Tejun Heo
2011-02-23 22:17 ` Yinghai Lu
2011-02-24 9:15 ` Tejun Heo
2011-02-25 1:37 ` Yinghai Lu
2011-02-25 1:38 ` [PATCH 1/2] x86,mm: Introduce init_memory_mapping_ext() Yinghai Lu
2011-02-25 6:20 ` [PATCH 2/2] x86,mm,64bit: Round up memory boundary for init_memory_mapping_high() Yinghai Lu
2011-02-25 10:03 ` Ingo Molnar
2011-02-25 20:22 ` Yinghai Lu [this message]
2011-02-26 3:06 ` [PATCH 1/3] x86, mm: Introduce global page_size_mask Yinghai Lu
2011-02-26 3:07 ` [PATCH 2/3] x86,mm: Introduce init_memory_mapping_ext() Yinghai Lu
2011-02-26 3:08 ` [PATCH 3/3] x86,mm,64bit: Round up memory boundary for init_memory_mapping_high() Yinghai Lu
2011-02-26 10:36 ` Tejun Heo
2011-02-26 10:55 ` Tejun Heo
2011-02-25 11:16 ` [PATCH 2/2] " Tejun Heo
2011-02-25 20:18 ` Yinghai Lu
2011-02-26 8:57 ` Tejun Heo
2011-02-27 11:53 ` Ingo Molnar
2011-02-28 18:14 ` questions about init_memory_mapping_high() H. Peter Anvin
2011-03-01 8:29 ` Tejun Heo
2011-03-01 19:44 ` 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=4D680F77.5060107@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox