From: Russell King <rmk+lkml@arm.linux.org.uk>
To: "Maciej W. Rozycki" <macro@linux-mips.org>, Russ Anderson <rja@sgi.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RCF] Linux memory error handling
Date: Wed, 15 Jun 2005 20:46:59 +0100 [thread overview]
Message-ID: <20050615204659.A14853@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.61L.0506151545410.13835@blysk.ds.pg.gda.pl>; from macro@linux-mips.org on Wed, Jun 15, 2005 at 04:26:13PM +0100
On Wed, Jun 15, 2005 at 04:26:13PM +0100, Maciej W. Rozycki wrote:
> On Wed, 15 Jun 2005, Russ Anderson wrote:
> > Memory DIMM information & settings:
> >
> > Use a /proc/dimm_info interface to pass DIMM information to Linux.
> > Hardware vendors could add their hardware specific settings.
>
> I'd recommend a more generic name rather than "dimm_info" if that is to
> be reused universally.
Agree.
I'd also suggest that there be some method to tell the kernel from
architecture code about this "dimm_info" stuff - many embedded
platforms already know their memory organisation.
BTW, Russ, could we have a better description of what information is
intended to be supplied?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-06-15 19:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 14:30 [RCF] Linux memory error handling Russ Anderson
2005-06-15 15:08 ` Andi Kleen
2005-06-15 16:36 ` Russ Anderson
2005-06-15 15:26 ` Maciej W. Rozycki
2005-06-15 19:46 ` Russell King [this message]
2005-06-15 20:28 ` [RFC] " Russ Anderson
2005-06-15 20:45 ` Dave Hansen
2005-06-15 21:27 ` Russ Anderson
2005-06-15 21:33 ` Dave Hansen
2005-06-20 20:42 ` Russ Anderson
2005-06-20 21:07 ` Dave Hansen
2005-06-15 22:09 ` Russ Anderson
2005-06-16 19:42 ` Maciej W. Rozycki
2005-06-16 1:03 ` [RCF] " Ross Biro
2005-06-15 20:42 ` Joel Schopp
2005-06-16 2:54 ` Wang, Zhenyu
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=20050615204659.A14853@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=rja@sgi.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