[lkml]   [2012]   [Mar]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 0/5] Persist printk buffer across reboots.
From: Avery Pennarun <>
Date: Tue, 13 Mar 2012 02:00:30 -0400

> Sounds good to me. Do you have any pointers? Just use an
> early_param? If we see the early_param but we can't reserve the
> requested address, should we fall back to probing or disable the
> PRINTK_PERSIST mode entirely?

The interface is prom_retain() in f.e. arch/sparc/prom/misc_64.c

You give it a string name, a size in bytes, and an alignment. And you
are given a physical address on success. I'm pretty sure the string
name you give is one of the keys it uses to look up the same piece of
memory for you next time. So you can have retained memory across soft
resets not just for log buffers, but for other things too.

The idea is that you call prom_retain() before you take a look at what
physical memory is available in the kernel, and the firmware takes
this physical chunk out of those available memory lists upon
prom_retain() success.

 \ /
  Last update: 2012-03-13 07:57    [W:0.077 / U:0.492 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site