Re: [PATCH v1 6/6] driver: Google Memory Console

[Greg KH]

On Mon, Jan 24, 2011 at 04:25:05PM -0800, Mike Waychison wrote:
> This patch introduces the 'memconsole' driver.
> 
> Our firmware gives us access to an in-memory log of the firmware's
> output.   This gives us visibility in a data-center of headless machines
> as to what the firmware is doing.
> 
> The memory console is found by the driver by finding a header block in
> the EBDA.  The buffer is then copied out, and is currently prepended
> to the kernel's dmesg ring-buffer.

Why does this have to be the first thing in the dmesg buffer?
What's wrong with it showing up whenever this driver is loaded like all
other drivers?

thanks,

greg k-h
--
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/