From: "Huang, Ying" <ying.huang@intel.com>
To: akpm@linux-foundation.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Chandramouli Narayanan <mouli@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/3 -v4] x86_64 EFI runtime service support
Date: Thu, 25 Oct 2007 14:57:40 +0800 [thread overview]
Message-ID: <1193295460.23935.201.camel@caritas-dev.intel.com> (raw)
Following sets of patches add EFI/UEFI (Unified Extensible Firmware
Interface) runtime services support to x86_64 architecture. The
patches have been tested against 2.6.24-rc1 kernel on Intel platforms
with EFI1.10 and UEFI2.0 firmware.
v4:
- EFI boot parameters are extended for 64-bit EFI in a 32-bit EFI
compatible way.
- Add EFI runtime services document.
v3:
- Remove E820_RUNTIME_CODE, the EFI memory map is used to deal with
EFI runtime code area.
- The method used to make EFI runtime code area executable is change:
a. Before page allocation is usable, the PMD of direct mapping is
changed temporarily before and after each EFI call.
b. After page allocation is usable, change_page_attr_addr is used to
change corresponding page attribute.
- Use fixmap to map EFI memory mapped IO memory area to make kexec
workable.
- Add a kernel command line option "noefi" to make it possible to turn
off EFI runtime services support.
- Function pointers are used for EFI time runtime service.
- EFI reboot runtime service is embedded into the framework of
reboot_type.
- A kernel command line option "noefi_time" is added to make it
possible to fall back to CMOS based implementation.
v2:
- The EFI callwrapper is re-implemented in assembler.
Best Regards,
Huang Ying
reply other threads:[~2007-10-25 6:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1193295460.23935.201.camel@caritas-dev.intel.com \
--to=ying.huang@intel.com \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mouli@linux.intel.com \
--cc=tglx@linutronix.de \
/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