public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Mike Waychison <mikew@google.com>
Cc: "H. Peter Anvin" <hpa@kernel.org>, Greg KH <greg@kroah.com>,
	Matt Domsch <Matt_Domsch@dell.com>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Duncan Laurie <dlaurie@google.com>,
	Aaron Durbin <adurbin@google.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org,
	Tim Hockin <thockin@google.com>, San Mehat <san@google.com>
Subject: Re: [PATCH v2 12/12] driver: Google Memory Console
Date: Mon, 14 Mar 2011 15:46:45 -0700	[thread overview]
Message-ID: <4D7E9AD5.1080902@zytor.com> (raw)
In-Reply-To: <AANLkTino-QB=2ctS4QFWQAr3gXTc5GfC5q5bQcFguVNs@mail.gmail.com>

On 03/14/2011 01:03 PM, Mike Waychison wrote:
> On Sun, Mar 13, 2011 at 9:54 PM, H. Peter Anvin <hpa@kernel.org> 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.
> 
> Good point.  I'll add some DMI strings checks.  It *should* be
> sufficient to just ensure that "Google, Inc." is the board vendor
> string (though I'll need to run some tests to verify that this covers
> the boards we care about).
> 

Sounds good.

	-hpa


  reply	other threads:[~2011-03-14 22:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-12  1:42 [PATCH v2 00/12] google firmware support Mike Waychison
2011-03-12  1:43 ` [PATCH v2 01/12] efivars: move efivars globals into struct efivars Mike Waychison
2011-03-12  1:43 ` [PATCH v2 02/12] efivars: Make efivars bin_attributes dynamic Mike Waychison
2011-03-12  1:43 ` [PATCH v2 03/12] efivars: parameterize efivars Mike Waychison
2011-03-12  1:43 ` [PATCH v2 04/12] efivars: Split out variable registration Mike Waychison
2011-03-12  1:43 ` [PATCH v2 05/12] efivars: Parameterize operations Mike Waychison
2011-03-12  1:43 ` [PATCH v2 06/12] efivars: Expose efivars functionality to external drivers Mike Waychison
2011-03-12  1:43 ` [PATCH v2 07/12] efivars: Add Documentation Mike Waychison
2011-03-12  1:43 ` [PATCH v2 08/12] x86: get_bios_ebda_length() Mike Waychison
2011-03-14 15:43   ` Greg KH
2011-03-12  1:43 ` [PATCH v2 09/12] x86: Better comments for get_bios_ebda() Mike Waychison
2011-03-14 15:43   ` Greg KH
2011-03-12  1:43 ` [PATCH v2 10/12] Introduce CONFIG_GOOGLE_FIRMWARE Mike Waychison
2011-03-14 15:45   ` Greg KH
2011-03-14 19:49     ` Mike Waychison
2011-03-14 19:59       ` Greg KH
2011-03-14 20:06         ` Mike Waychison
2011-03-12  1:43 ` [PATCH v2 11/12] driver: Google EFI SMI Mike Waychison
2011-03-14 15:47   ` Greg KH
2011-03-14 20:01     ` Mike Waychison
2011-03-14 20:13       ` Greg KH
2011-03-14 21:09         ` Mike Waychison
2011-03-14 23:05         ` Alan Cox
2011-03-12  1:43 ` [PATCH v2 12/12] driver: Google Memory Console Mike Waychison
2011-03-14  4:54   ` H. Peter Anvin
2011-03-14  4:58     ` Tim Hockin
2011-03-14  5:02       ` H. Peter Anvin
2011-03-14  9:22         ` Ingo Molnar
2011-03-14 14:01           ` Tim Hockin
2011-03-14 14:23             ` Ingo Molnar
2011-03-14 15:47               ` Greg KH
2011-03-14 20:03     ` Mike Waychison
2011-03-14 22:46       ` H. Peter Anvin [this message]
2011-03-12  3:54 ` [PATCH v2 00/12] google firmware support Matt Domsch
2011-03-14 15:42   ` Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D7E9AD5.1080902@zytor.com \
    --to=hpa@zytor.com \
    --cc=Matt_Domsch@dell.com \
    --cc=adurbin@google.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dlaurie@google.com \
    --cc=greg@kroah.com \
    --cc=hpa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikew@google.com \
    --cc=san@google.com \
    --cc=thockin@google.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox