Andi Kleen wrote:
On Fri, Apr 15, 2005 at 11:43:55AM +0530, Hariprasad Nellitheertha wrote:
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached
Andi Kleen wrote:
On Fri, Apr 15, 2005 at 11:43:55AM +0530, Hariprasad Nellitheertha wrote:
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached
On Fri, Apr 15, 2005 at 11:43:55AM +0530, Hariprasad Nellitheertha wrote:
> Hi Andi,
>
> In order to port kdump to x86_64, we need to have the
> memmap= kernel command line option available. This is so
> that the dump-capture kernel can be booted with a custom
> memory map.
>
> The attached
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached patch adds the memmap= functionality to the
x86_64 kernel. It is against 2.6.12-rc2-mm3. I
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached patch adds the memmap= functionality to the
x86_64 kernel. It is against 2.6.12-rc2-mm3. I
On Fri, Apr 15, 2005 at 11:43:55AM +0530, Hariprasad Nellitheertha wrote:
Hi Andi,
In order to port kdump to x86_64, we need to have the
memmap= kernel command line option available. This is so
that the dump-capture kernel can be booted with a custom
memory map.
The attached patch
6 matches
Mail list logo
