From: Greg KH <greg@kroah.com>
To: Doug Thompson <norsk5@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Mon, 14 Nov 2005 14:31:05 -0800 [thread overview]
Message-ID: <20051114223105.GA5868@kroah.com> (raw)
In-Reply-To: <20051114221419.10324.qmail@web50101.mail.yahoo.com>
On Mon, Nov 14, 2005 at 02:14:19PM -0800, Doug Thompson wrote:
>
> I am trying to design the sysfs interface tree for the
> new set of EDAC modules that are waiting for this
> interface, before being put into the kernel.
>
> Currently the original EDAC (bluesmoke) has its own
> /proc directory (/proc/mc) with files and a directory
> (0,1,2,...)for each memory controller on the system.
> This will be removed and the new information interface
> will be placed in the sysfs.
>
> One proposal is to place the information in
> /sys/devices/system in the following directories:
Why not use /sys/firmware/ instead?
Or do you want to use the struct device stuff?
> For EDAC general memory ECC controls and information
> files:
>
> /sys/devices/systems/edac/mc/
What kind of controls and files?
>
> For PCI Parity Error detection controls and
> information files:
>
> /sys/devices/system/edac/pci
That kind of controls and files?
> In addition /sys/devices/system/edac/mc/ would have
> directories:
>
> mc0/
> mc1/
> ...
>
> for each memory controller's specific controls and
> information.
Again, what kind of controls and information?
> Currently the similiar error detection device
> /sys/devices/system/machinecheck resides here are
> well.
>
>
> The alternative layout would be to use the /sys/class
> directory when nested-classes become available:
They are in 2.6.15-rc1, but you _really_ don't want to use them, they
are a huge pain, and I will be getting rid of them, along with all
struct class_device stuff in the near future. See the archives for
details, or it's summarized here:
http://www.kroah.com/log/linux/driver_model_changes.html
>
> /sys/class/edac/mc/...
>
> and
>
> /sys/class/edac/pci/...
>
> But edac doesn't quite seem to fit here.
I agree.
> I have failed to date to really find a policy or set
> of rules of use for the sysfs as to what goes where
> for such items as EDAC. After searching the web,
> articles and thinking about this for some time now, I
> am requesting comments on the sysfs model for where
> EDAC would fit best.
What exactly does EDAC do (and what does it stand for anyway?)
thanks,
greg k-h
next prev parent reply other threads:[~2005-11-14 22:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:14 [RFC] EDAC and the sysfs Doug Thompson
2005-11-14 22:31 ` Greg KH [this message]
2005-11-15 0:30 ` Dave Jones
2005-11-15 17:24 ` Greg KH
2005-11-15 0:47 ` Doug Thompson
2005-11-15 1:12 ` Doug Thompson
2005-11-15 17:25 ` Greg KH
2005-11-16 0:26 ` Doug Thompson
2005-11-17 7:05 ` Greg KH
2005-11-17 17:20 ` Doug Thompson
2005-11-17 17:18 ` Greg KH
2005-11-17 18:32 ` Kay Sievers
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=20051114223105.GA5868@kroah.com \
--to=greg@kroah.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.