Re: [PATCH 2/2] efi/arm*: use memremap() to create the persistent memmap mapping

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 14 Apr, at 10:43:45AM, Ard Biesheuvel wrote:
> 
> Actually, this patch does not depend on the ARM memremap changes being
> merged: before those changes, memremap() unconditionally falls back to
> ioremap_cache() for 'System RAM' so this patch is essentially a nop in
> that case. This is guaranteed to work due to the fact that we [still]
> use MEMBLOCK_NOMAP for mapping the memory map on ARM.
 
OK, these two look good to me, so I'm going to queue them up in 'next'
chronologically before your EFI Memory Attributes table patches.

> The memory attributes table and GOP changes do depend on it, however,
> since the configuration tables it accesses are likely to be covered by
> a struct page, in which case ARM disallows the ioremap_cache() (and
> thus the use of memremap() until it is updated to deal with this
> situation explicitly)
> 
> The other change that depends on it is dropping the MEMBLOCK_NOMAP for
> ARM as well (as we did in the arm64 patch that is currently queued up
> for v4.6-rc)

Noted. Thanks Ard.
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux