[lkml]   [2013]   [Oct]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 12/12] EFI: Runtime services virtual mapping
On Fri, Oct 11, 2013 at 02:24:37PM +0800, Dave Young wrote:
> But for current implementation from Boris, getting same mapping
> between diffrent kernel depends on same md order (same start and
> size for each one) How about using this mapping solution but at the
> same time for kexec kernel we also pass the virtual mappings via
> setup_data, only thing diffrent is we only need map the non boot
> region and just use the boot region size to ensure the other regions
> are mapped with same virtual address.

Actually, as hpa suggested, we will need to be passing the explicit
virtual addresses to the kexec kernel in case we change the mapping
algorithm in the future. So all should go through setup_data.

> OTOH, if we only passing ioremapped data without Boris's current patch
> the problem I worry about is how can we ensure the addresses are not
> used by other code before we mapping the in 2nd kernel efi_init.

Right, the old method of mapping EFI runtime regions used ioremap and
was mapping the regions in the same address space. Now we have reserved
a 64G in the VA space ending at -4G (i.e. 0xffff_ffff_0000_0000) which
is reserved only for EFI RT usage.


Sent from a fat crate under my desk. Formatting is fine.

 \ /
  Last update: 2013-10-11 10:01    [W:0.127 / U:0.360 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site