On Mon, Jan 12, 2015 at 10:29:19AM -0500, Vivek Goyal wrote: > Kdump has the notion of backup region. Where certain parts of old kernels > memory can be moved to a different location (first 640K on x86 as of now) > and new kernel can make use of this memory now. > > So we will have to just make sure that no parts of this old page table > fall into backup region. Uuh, looks like the 'iommu-with-kdump-issue' isn't complicated enough yet ;) Sadly, your above statement is true for all hardware-accessible data structures in IOMMU code. I think about how we can solve this, is there an easy way to allocate memory that is not in any backup region? Thanks, Joerg
