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 08:03:46 -0700 [thread overview]
Message-ID: <20080630150346.GF10571@ajones-laptop.nbttech.com> (raw)
In-Reply-To: <77374.55758.qm@web50103.mail.re2.yahoo.com>
Hi Doug, ...
On Fri, Jun 27, 2008 at 11:15:06PM -0700, Doug Thompson wrote:
>
> --- Andi Kleen <andi@firstfloor.org> wrote:
>
> > dougthompson@xmission.com writes:
> > >
> > > 2) I have not yet tackled the de-interleaving of the
> > > rank/controller address space into the physical address
> > > space of the CPU. There is nothing fundamentally missing,
> > > it is just ending up to be a lot of code, and I'd rather
> > > keep it separate for now, esp since it doesn't work yet...
> > >
> > > 3) The code depends on a particular i5100 chip select
> > > to DIMM mainboard chip select mapping. This mapping
> > > seems obvious to me in order to support dual and single
> > > ranked memory, but it is not unique and DIMM labels
> > > could be wrong on other mainboards. There is no way
> > > to query this mapping that I know of.
> >
> > Since there's a non negligible probability that the output
> > of this driver is completely misleading because of (2) and (3)
> > and probably (4) too [reporting the wrong DIMMs etc.]
> > would it be possible to add some flag to EDAC that
> > warns the user that the output is not fully reliable?\
>
> good idea.
>
> 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?
How do they get around these issues?
Thanks...
Arthur
> >
> > -Andi (who can just see people replacing the wrong DIMMs and
> > then blaming Linux)
> >
> >
>
>
> W1DUG
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://sourceforge.net/services/buy/index.php
> _______________________________________________
> bluesmoke-devel mailing list
> bluesmoke-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluesmoke-devel
next prev parent reply other threads:[~2008-06-30 15:03 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 [this message]
2008-06-30 19:58 ` Doug Thompson
2008-06-30 20:13 ` Arthur Jones
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=20080630150346.GF10571@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®