From: Toshi Kani <toshi.kani@hp.com>
To: Dave Young <dyoung@redhat.com>
Cc: mjg59@srcf.ucam.org, linux-efi@vger.kernel.org,
matt@console-pimps.org, greg@kroah.com, x86@kernel.org,
kexec@lists.infradead.org, James.Bottomley@HansenPartnership.com,
horms@verge.net.au, bp@alien8.de, ebiederm@xmission.com,
hpa@zytor.com, vgoyal@redhat.com
Subject: Re: [PATCH v4 0/4] kexec-tools: efi runtime support on kexec kernel
Date: Fri, 20 Dec 2013 10:58:13 -0700 [thread overview]
Message-ID: <1387562293.21140.55.camel@misato.fc.hp.com> (raw)
In-Reply-To: <1387533947-18210-1-git-send-email-dyoung@redhat.com>
On Fri, 2013-12-20 at 18:05 +0800, Dave Young wrote:
> This patchset is for adding efi runtime support on kexec kernel
> kernel patches see below thread:
> http://thread.gmane.org/gmane.linux.kernel.efi/2491
>
> in kexec-tools, this patchset will do below:
> 1. retrieve efi_info from debugfs boot_params, and fill the
> x86 setup header
>
> 2. collect data efi runtime needed:
> /sys/firmware/efi/systab: fw_vendor, runtime, config_tables and smbios
> /sys/firmware/efi/efi-runtime-map/*, the phys-virt mappings in 1st kernel
>
> 3. assemble setup_data based on data get in 2) then pass it to 2nd kernel
>
> changelog v3->v4:
> update efi_info memmap to the saved runtime map instead of use 1st kernel
> untouched memmap.
>
> Tested on OVMF, dell laptop, lenovo laptop and HP workstation
>
> Dave Young (4):
> build fix: include x86-linux.h in x86-linux-setup.h
> Add function get_bootparam
> Add efi_info in x86 setup header
> Passing efi related data via setup_data
>
> include/x86/x86-linux.h | 3 +-
> kexec/arch/i386/crashdump-x86.c | 4 +-
> kexec/arch/i386/x86-linux-setup.c | 246 ++++++++++++++++++++++++++++++++++--
> kexec/arch/i386/x86-linux-setup.h | 2 +
> kexec/arch/x86_64/kexec-bzImage64.c | 6 +
> 5 files changed, 248 insertions(+), 13 deletions(-)
>
Tested on an HP 60-way UEFI platform. For the series:
Tested-by: Toshi Kani <toshi.kani@hp.com>
Thanks,
-Toshi
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-12-20 18:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 10:05 [PATCH v4 0/4] kexec-tools: efi runtime support on kexec kernel Dave Young
2013-12-20 10:05 ` [PATCH v4 1/4] build fix: include x86-linux.h in x86-linux-setup.h Dave Young
2013-12-20 10:05 ` [PATCH v4 2/4] Add function get_bootparam Dave Young
2013-12-20 10:05 ` [PATCH v4 3/4] Add efi_info in x86 setup header Dave Young
2013-12-20 10:05 ` [PATCH v4 4/4] Passing efi related data via setup_data Dave Young
2013-12-30 7:16 ` [PATCH v4 4/4 update] " Dave Young
2014-01-06 21:58 ` Toshi Kani
2013-12-20 17:58 ` Toshi Kani [this message]
2014-01-21 2:55 ` [PATCH v4 0/4] kexec-tools: efi runtime support on kexec kernel Dave Young
2014-01-21 5:07 ` Simon Horman
2014-01-21 6:13 ` Dave Young
2014-01-21 6:31 ` Simon Horman
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=1387562293.21140.55.camel@misato.fc.hp.com \
--to=toshi.kani@hp.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=ebiederm@xmission.com \
--cc=greg@kroah.com \
--cc=horms@verge.net.au \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=linux-efi@vger.kernel.org \
--cc=matt@console-pimps.org \
--cc=mjg59@srcf.ucam.org \
--cc=vgoyal@redhat.com \
--cc=x86@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