From: "H. Peter Anvin" <hpa@zytor.com>
To: Takao Indoh <indou.takao@jp.fujitsu.com>
Cc: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
horms@verge.net.au, nhorman@tuxdriver.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, ebiederm@xmission.com, tglx@linutronix.de,
vgoyal@redhat.com
Subject: Re: [PATCH v2][EFI] Run EFI in physical mode
Date: Thu, 16 Dec 2010 12:22:14 -0800 [thread overview]
Message-ID: <4D0A74F6.6070002@zytor.com> (raw)
In-Reply-To: <9CB9BB8ED64BAindou.takao@jp.fujitsu.com>
On 12/14/2010 10:01 AM, Takao Indoh wrote:
> On Tue, 14 Dec 2010 12:43:58 +0900, Kenji Kaneshige wrote:
>
>> Hi,
>>
>> I tested this patch on the system that has large amount of memory (1TB),
>> and I encountered the immediate system reset problem that happens every
>> time I modify the EFI boot entry using efibootmgr command. It seems that
>> triple fault happens due to the incorrect page table setup.
>>
>>> +void __init efi_pagetable_init(void)
>>> +{
>> (snip.)
>>> + pgd = efi_pgd + pgd_index(PAGE_OFFSET);
>>> + set_pgd(pgd, *pgd_offset_k(PAGE_OFFSET));
>>> + pgd = efi_pgd + pgd_index(__START_KERNEL_map);
>>> + set_pgd(pgd, *pgd_offset_k(__START_KERNEL_map));
>>> +}
>>
>> Maybe we need to map whole kernel address space. The problem doesn't
>> happen by modifying as follows.
>>
>> clone_pgd_range(efi_pgd + KERNEL_PGD_BOUNDARY,
>> swapper_pg_dir + KERNEL_PGD_BOUNDARY,
>> KERNEL_PGD_PTRS);
>
> Agree, I'll merge this to the patch. And I got another bug report. This
> should be also merged.
>
>
> @@ -177,8 +177,8 @@ void __init efi_pagetable_init(void)
> memset(efi_pgd, 0, sizeof(efi_pgd));
> for (p = memmap.map; p < memmap.map_end; p += memmap.desc_size) {
> md = p;
> - if (!(md->type & EFI_RUNTIME_SERVICES_CODE) &&
> - !(md->type & EFI_RUNTIME_SERVICES_DATA))
> + if ((md->type != EFI_RUNTIME_SERVICES_CODE) &&
> + (md->type != EFI_RUNTIME_SERVICES_DATA))
> continue;
>
> start_pfn = md->phys_addr >> PAGE_SHIFT;
> @@ -191,7 +191,7 @@ void __init efi_pagetable_init(void)
> pud = fill_pud(pgd, vaddr);
> pmd = fill_pmd(pud, vaddr);
> pte = fill_pte(pmd, vaddr);
> - if (md->type & EFI_RUNTIME_SERVICES_CODE)
> + if (md->type == EFI_RUNTIME_SERVICES_CODE)
> set_pte(pte, pfn_pte(pfn, PAGE_KERNEL_EXEC));
> else
> set_pte(pte, pfn_pte(pfn, PAGE_KERNEL));
>
Note: the current kernel has initial_page_table around for 32 bits; we
should do the equivalent for 64 bits and always keep a 1:1 page table
set around instead of having a special page table. As such, I would
prefer to not merge a patchset that adds yet another set of ad hoc page
tables if at all possible.
-hpa
next prev parent reply other threads:[~2010-12-16 20:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 23:07 [PATCH v2][EFI] Run EFI in physical mode Takao Indoh
2010-12-14 3:43 ` Kenji Kaneshige
2010-12-14 18:01 ` Takao Indoh
2010-12-16 20:22 ` H. Peter Anvin [this message]
2011-01-13 16:38 ` Matthew Garrett
2011-01-13 17:16 ` Eric W. Biederman
2011-01-13 17:41 ` Matthew Garrett
2010-12-14 22:38 ` Takao Indoh
2010-12-15 23:42 ` Eric W. Biederman
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=4D0A74F6.6070002@zytor.com \
--to=hpa@zytor.com \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=indou.takao@jp.fujitsu.com \
--cc=kaneshige.kenji@jp.fujitsu.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nhorman@tuxdriver.com \
--cc=tglx@linutronix.de \
--cc=vgoyal@redhat.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