From: Matt Fleming <matt.fleming@intel.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "H. Peter Anvin" <hpa@kernel.org>,
mingo@redhat.com, mjg@redhat.com, linux-kernel@vger.kernel.org,
keithp@keithp.com, rui.zhang@intel.com,
huang.ying.caritas@gmail.com, stable@vger.kernel.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86, efi: Delete efi_ioremap() and fix CONFIG_X86_32 oops
Date: Fri, 16 Mar 2012 18:36:46 +0000 [thread overview]
Message-ID: <1331923006.4041.30.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <CAE9FiQVWjZFA9gz43NJAKbvp7HT0oekXiRY5mPgg6O8EN5xb7g@mail.gmail.com>
On Thu, 2012-03-15 at 10:54 -0700, Yinghai Lu wrote:
> > if (end <= max_low_pfn << PAGE_SHIFT)
> > max_low_pfn_mapped = last_pfn_mapped;
>
> why max_low_pfn is used here?
The idea is that we only want to update max_low_pfn_mapped when we've
mapped a region at or below max_low_pfn. This maintains compatibility
with behaviour prior to this patch.
> > The max_low_pfn checks are only for CONFIG_X86_32 so that the behaviour
> > is the same as before this patch, i.e. we don't try to map above
> > max_low_pfn.
>
> ok, to simplify the code, in setup.c you could move
> #ifdef CONFIG_X86_64
> if (max_pfn > max_low_pfn) {
> /* can we preseve max_low_pfn ?*/
> max_low_pfn = max_pfn;
> }
> #endif
>
> before calling new init_memory_mapping()...
>
> so you could remove the #idef. in init_memory_mapping.
Hmm.. if we do this then max_low_pfn_mapped will be set to max_pfn on
CONFIG_X86_64 by the time we've finished looping in
init_memory_mapping(). This is not how things work currently. Will that
cause a problem?
next prev parent reply other threads:[~2012-03-16 18:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 13:30 [PATCH] " Matt Fleming
2012-02-23 1:16 ` [tip:x86/urgent] " tip-bot for Matt Fleming
2012-02-23 2:20 ` Yinghai Lu
2012-02-23 3:32 ` H. Peter Anvin
2012-02-23 10:36 ` Yinghai Lu
2012-02-24 4:47 ` H. Peter Anvin
2012-02-28 2:27 ` H. Peter Anvin
2012-03-07 10:30 ` Matt Fleming
2012-03-07 18:05 ` Yinghai Lu
2012-03-08 11:28 ` Matt Fleming
2012-03-08 18:59 ` Yinghai Lu
2012-03-12 12:38 ` Matt Fleming
2012-03-13 5:39 ` Yinghai Lu
2012-03-15 12:40 ` Matt Fleming
2012-03-15 17:54 ` Yinghai Lu
2012-03-16 18:36 ` Matt Fleming [this message]
2012-03-16 19:01 ` Yinghai Lu
2012-03-07 18:14 ` Yinghai Lu
2012-03-07 18:18 ` Matthew Garrett
2012-03-08 12:09 ` Matt Fleming
2012-03-04 0:12 ` Keith Packard
2012-03-04 0:27 ` H. Peter Anvin
2012-03-04 1:33 ` Keith Packard
2012-03-05 10:45 ` Ingo Molnar
2012-03-07 18:31 ` Yinghai Lu
2012-03-05 11:48 ` Matt Fleming
2012-02-28 2:33 ` [PATCH] " H. Peter Anvin
2012-02-28 17:35 ` Matt Fleming
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=1331923006.4041.30.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt.fleming@intel.com \
--cc=hpa@kernel.org \
--cc=huang.ying.caritas@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjg@redhat.com \
--cc=rui.zhang@intel.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@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
Powered by JetHome