From: "Huang, Ying" <ying.huang@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: akpm@linux-foundation.org, Yinghai Lu <yhlu.kernel@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Chandramouli Narayanan <mouli@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] x86_64 EFI support -v3: EFI boot support
Date: Wed, 01 Aug 2007 16:59:08 +0800 [thread overview]
Message-ID: <1185958748.1363.40.camel@caritas-dev.intel.com> (raw)
In-Reply-To: <200707311335.40235.ak@suse.de>
On Tue, 2007-07-31 at 13:35 +0200, Andi Kleen wrote:
> > static unsigned long dma_reserve __initdata;
> > +/* Flag indicating EFI runtime executable code area */
> > +static int efi_runtime_code_area;
>
> We don't normally use globals to modify function behaviour.
>
> >
> > DEFINE_PER_CPU(struct mmu_gather, mmu_gathers);
> >
> > @@ -199,7 +202,7 @@
> > static __meminit void unmap_low_page(void *adr)
> > {
> >
> > - if (after_bootmem)
> > + if (after_bootmem || efi_runtime_code_area)
> > return;
> >
> > early_iounmap(adr, PAGE_SIZE);
> > @@ -259,16 +262,21 @@
> > pmd_t *pmd = pmd_page + pmd_index(address);
> >
> > if (address >= end) {
> > - if (!after_bootmem)
> > + if (!after_bootmem && !efi_runtime_code_area)
>
>
> This one seems also weird. Are you sure this doesn't remove _NX from
> more than the intended area?
>
> > for (; i < PTRS_PER_PMD; i++, pmd++)
> > set_pmd(pmd, __pmd(0));
> > break;
> > }
> >
> > - if (pmd_val(*pmd))
> > + if (pmd_val(*pmd) && !efi_runtime_code_area)
> > continue;
> >
> > - entry = _PAGE_NX|_PAGE_PSE|_KERNPG_TABLE|_PAGE_GLOBAL|address;
> > + if (efi_runtime_code_area) {
> > + entry = pmd_val(*pmd);
> > + entry &= ~_PAGE_NX;
> > + } else
> > + entry = _PAGE_NX | _PAGE_PSE | _KERNPG_TABLE | \
> > + _PAGE_GLOBAL | address;
>
> This doesn't look correct. PSE/KERNPG/GLOBAL/address surely need to be set
> for EFI areas too.
>
> The changes to this file are quite messy.
> Perhaps it would be better if you just use change_page_attr() afterwards.
> This would make it using 4K pages instead of 2MB, but that wouldn't be a catastrophe.
The memory area mapping must be changed before time_init, where the
first EFI runtime serivce (efi_get_time) is called. But
"change_page_attr" can not be used there, because "alloc_pages" is used
by "change_page_attr".
Should I change "change_page_attr" to make it work before "mem_init"? Or
Should I change "init_memory_mapping" to make it can be used to change
mapping attributes? Which one is better?
> What exactly are you trying to do here? Just remove _NX for some areas?
Yes. I just want to remove _NX for some areas.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2007-08-01 9:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 3:12 [PATCH 2/5] x86_64 EFI support -v3: EFI boot support Huang, Ying
2007-07-31 11:35 ` Andi Kleen
2007-08-01 8:59 ` Huang, Ying [this message]
2007-08-01 12:56 ` Andi Kleen
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=1185958748.1363.40.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mouli@linux.intel.com \
--cc=randy.dunlap@oracle.com \
--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