Hello Ard, On Thu, Dec 3, 2015 at 4:55 PM, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote: > On 30 November 2015 at 13:28, Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> wrote: >> This introduces the MEMBLOCK_NOMAP attribute and the required plumbing >> to make it usable as an indicator that some parts of normal memory >> should not be covered by the kernel direct mapping. It is up to the >> arch to actually honor the attribute when laying out this mapping, >> but the memblock code itself is modified to disregard these regions >> for allocations and other general use. >>.... > May I kindly ask team-mm/Andrew/Alexander to chime in here, and > indicate whether you are ok with this patch going in for 4.5? If so, > could you please provide your ack so the patch can be kept together > with the rest of the series, which depends on it? > > I should note that this change should not affect any memblock users > that never set the MEMBLOCK_NOMAP flag, but please, if you see any > issues beyond 'this may conflict with other stuff we have queued for > 4.5', please do let me know. Just tested the kernel with this patch with qemu and real hardware and it works, nothing does not brake for me. -- 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
