mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arthur Jones <ajones@riverbed.com>
To: Doug Thompson <norsk5@yahoo.com>
Cc: Andi Kleen <andi@firstfloor.org>,
	"dougthompson@xmission.com" <dougthompson@xmission.com>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"bluesmoke-devel@lists.sourceforge.net" 
	<bluesmoke-devel@lists.sourceforge.net>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/13] EDAC i5100 new intel chipset driver
Date: Mon, 30 Jun 2008 13:13:40 -0700	[thread overview]
Message-ID: <20080630201340.GI10571@ajones-laptop.nbttech.com> (raw)
In-Reply-To: <262167.11235.qm@web50105.mail.re2.yahoo.com>

Hi Doug,  ...

On Mon, Jun 30, 2008 at 12:58:59PM -0700, Doug Thompson wrote:
> 
> --- Arthur Jones <ajones@riverbed.com> wrote:
> 
> > > Arthur, could you add some more text to the driver's output, before the call to the
> > > core's output function, doing exactly that? Explaining just what you DO know, and what you
> > don't
> > > know?
> >
> > Everything should be good except the DIMM label.  There
> > are all kinds of ways this could be wrong (mainboard labelling,
> > mainboard routing, ...).  I think it might be better just
> > to leave this blank.
> >
> > Are there any EDAC drivers that properly report the DIMM label?
> 
> The drivers don't print the information just because of these issues. The labeling action is left
> to user space via edac-utils.  The label attributes in sysfs are initialized via a bootup daemon.
> Thereby EDAC (and the driver) provides a mechanism of storing the DIMM Label. (The driver is free
> to populate label if it so chooses, but that too could be overridden by userspace).
> 
> One driver I did for the Sicortex MIPS cluster only had TWO DIMMS, "East" and "West" on a 6 core
> processor card. The driver labeled those inside itself.
> 
> >
> > How do they get around these issues?
> 
> Late binding. Allow the setting of the label by userspace. edac-utils utilizes a file database of
> motherboards, which must be maintained yes, but it is flexible. An additional userspace program
> could source the labels via another mechanism.
> 
> Lawrence Livermore National Labs has tens of thousands of nodes, with 2, 4 or 8 CPUs per node, and
> they are the ones who developed the edac-utils userspace daemon and scripts.
> 
> http://sourceforge.net/projects/edac-utils/
> 
> The model for EDAC modules IS to leave the DIMM label blank for late binding of that information.

Thanks, I didn't know about edac-utils, that sounds much better
than what I was proposing.  I'll go have a look...

Given this, I think it would be best to pull out the labels from
the driver.  I'll see if I can put together a patch for that today
or tomorrow...

Arthur

  reply	other threads:[~2008-06-30 20:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 18:12 dougthompson
2008-06-27 23:05 ` Andrew Morton
2008-06-30 15:08   ` Arthur Jones
2008-06-28  5:07 ` Andi Kleen
2008-06-28  6:15   ` Doug Thompson
2008-06-30 15:03     ` Arthur Jones
2008-06-30 19:58       ` Doug Thompson
2008-06-30 20:13         ` Arthur Jones [this message]
2008-06-30 15:23     ` Arthur Jones
2008-06-30 15:01   ` Arthur Jones

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=20080630201340.GI10571@ajones-laptop.nbttech.com \
    --to=ajones@riverbed.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=bluesmoke-devel@lists.sourceforge.net \
    --cc=dougthompson@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=norsk5@yahoo.com \
    /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

all inboxes | Powered by JetHome®