Prev: Analysing an ARM perf.data file on a x86-64 workstation
Next: issues with kmemleak backport
From: Christoph Lameter on 19 Jan 2010 13:10
Thats good regardless and easy to review

Reviewed-by: Christoph Lameter <cl(a)linux-foundation.org>


On Fri, 15 Jan 2010, Yinghai Lu wrote:

> ---
> arch/x86/kernel/e820.c | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
> index c5c52da..62235e7 100644
> --- a/arch/x86/kernel/e820.c
> +++ b/arch/x86/kernel/e820.c
> @@ -1127,6 +1127,9 @@ void __init e820_reserve_resources_late(void)
> end = MAX_RESOURCE_SIZE;
> if (start >= end)
> continue;
> + printk(KERN_DEBUG "reserve RAM buffer: %016Lx - %016Lx ",
> + (unsigned long long) start,
> + (unsigned long long) end);
> reserve_region_with_split(&iomem_resource, start, end,
> "RAM buffer");
> }
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: Analysing an ARM perf.data file on a x86-64 workstation
Next: issues with kmemleak backport