[lkml]   [2011]   [Mar]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v2 12/12] driver: Google Memory Console
    "Sufficient" or not, that's how the BIOSes we've got work.  We can't
    retrofit that.

    On Sun, Mar 13, 2011 at 9:54 PM, H. Peter Anvin <> wrote:
    > On 03/11/2011 05:43 PM, 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 exported to userland in
    >> the file /sys/firmware/log.
    > OK, I really don't like this.
    > All it has is a 32-bit nonrandom signature, no DMI keying or anything
    > else to protect it.  This really isn't sufficient.
    >        -hpa
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2011-03-14 06:01    [W:0.028 / U:2.168 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site