From: "huang ying" <huang.ying.caritas@gmail.com>
To: "Yinghai Lu" <yinghai@kernel.org>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Huang Ying" <ying.huang@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] x86: make 64bit efi to use ioremap_cache for efi_ioremap
Date: Sun, 5 Oct 2008 16:56:32 +0800 [thread overview]
Message-ID: <851fc09e0810050156y114007e4hbdf3e6c5562004d3@mail.gmail.com> (raw)
In-Reply-To: <86802c440810041044m5b950721s8700bb6cd2fe75d@mail.gmail.com>
On Sun, Oct 5, 2008 at 1:44 AM, Yinghai Lu <yinghai@kernel.org> wrote:
> On Sat, Oct 4, 2008 at 2:35 AM, huang ying <huang.ying.caritas@gmail.com> wrote:
[...]
>> Using __va and efi_ioremap() here is to make EFI support compatible
>> with kexec. Because EFI provide only efi_enter_virtual_mode(), no
>> efi_leave_virtual_mode(), we should make EFI runtime memory area
>> mapped to same virtual memory area in original kernel and kexeced
>> kernel, so that the EFI runtime services can be used in kexeced
>> kernel.
>
> so need to make efi range all under direct-mapping like E820-RAM?
Some EFI runtime range is just some RAM area used by EFI runtime
services, they can be direct-mapped. Some EFI runtime range may be IO
MEM range used by EFI runtime services, it is possible that these IO
MEM range can not be direct-mapped. So I implement efi_ioremap() to
deal with them.
Best Regards,
Huang Ying
next prev parent reply other threads:[~2008-10-05 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-04 6:23 Yinghai Lu
2008-10-04 8:46 ` Ingo Molnar
2008-10-04 9:35 ` huang ying
2008-10-04 17:44 ` Yinghai Lu
2008-10-05 8:56 ` huang ying [this message]
2008-10-05 10:04 ` Ingo Molnar
2008-10-06 1:47 ` Huang Ying
2008-10-05 18:04 ` Yinghai Lu
2008-10-06 1:50 ` Huang Ying
2008-12-11 20:41 Jonathan Barkelew
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=851fc09e0810050156y114007e4hbdf3e6c5562004d3@mail.gmail.com \
--to=huang.ying.caritas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
--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
all inboxes | Powered by JetHome®