From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH -v2] EFI: Runtime services virtual mapping Date: Mon, 30 Sep 2013 22:17:30 +0200 Message-ID: <20130930201730.GD16383@pd.tnic> References: <52422A6A.8080305@zytor.com> <20130926031242.GA4487@dhcp-16-126.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Return-path: Content-Disposition: inline In-Reply-To: <20130926031242.GA4487-je1gSBvt1TcFLmT5oZ11vB/sF2h8X+2i0E9HWUfgJXw@public.gmane.org> Sender: linux-efi-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Dave Young Cc: "H. Peter Anvin" , X86 ML , LKML , Borislav Petkov , Matt Fleming , Matthew Garrett , James Bottomley , Vivek Goyal , linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-Id: linux-efi@vger.kernel.org On Thu, Sep 26, 2013 at 11:12:42AM +0800, Dave Young wrote: > If we choose this approach, can we save not only the efi_mapping, but > also the fields which will be converted to virt addr, like fw_vendor, > runtime, tables? During my test on a HP workstation, the config table > item (SMBIOS) also is converted to virt addr though spec only mention > fw_vendor/runtime/tables. Btw, I was about to ask: how do you pass boot_params to the kexec kernel? Because I'm looking into hpa's idea to pass an efi_mapping array of regions with setup_data but how does this get passed to the kexec'ed kernel? I see in your patches you have boot_params.saved_*** for the needed info but you're not writing to them anywhere. Is that why you've added them to the systab_show function so that userspace can parse it and build the boot_params thing? Thanks. -- Regards/Gruss, Boris. Sent from a fat crate under my desk. Formatting is fine. --