Re: [Fastboot] [PATCH] Reserving backup region for kexec basedcrashdumps.

[Vivek Goyal]

Hi,

On Thu, 2005-02-03 at 12:32, Hirokazu Takahashi wrote:
> Hi Vivek and Eric,
> 
> IMHO, why don't we swap not only the contents of the top 640K
> but also kernel working memory for kdump kernel?


Initial patches of kdump had adopted the same approach but given the
fact devices are not stopped during transition to new kernel after a
panic, it carried inherent risk of some DMA going on and corrupting the
new kernel/data structures. Hence the idea of running the kernel from a
reserved location came up. This should be DMA safe as long as DMA is not
misdirected.

Thanks 
Vivek

> 
> I guess this approach has some good points.
> 
>  1.Preallocating reserved area is not mandatory at boot time.
>    And the reserved area can be distributed in small pieces
>    like original kexec does.
> 
>  2.Special linking is not required for kdump kernel.
>    Each kdump kernel can be linked in the same way,
>    where the original kernel exists.
> 
> Am I missing something?
>  physical memory
>    +-------+
>    | 640K  ------------+
>    |.......|           |
>    |       |         copy
>    +-------+           |
>    |       |           |
>    |original<-----+    |
>    |kernel |      |    |
>    |       |      |    |
>    |.......|      |    |
>    |       |      |    |
>    |       |      |    |
>    |       |     swap  |
>    |       |      |    |
>    +-------+      |    |
>    |reserved<----------+
>    |area   |      |
>    |       |      |
>    |kdump  |<-----+
>    |kernel |
>    +-------+
>    |       |
>    |       |
>    |       |
>    +-------+
> 
> 


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/