From: Doug Thompson <norsk5@yahoo.com>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] EDAC and the sysfs
Date: Tue, 15 Nov 2005 16:26:38 -0800 (PST) [thread overview]
Message-ID: <20051116002638.762.qmail@web50106.mail.yahoo.com> (raw)
In-Reply-To: <20051115172528.GB13658@kroah.com>
--- Greg KH <greg@kroah.com> wrote:
> On Mon, Nov 14, 2005 at 04:47:03PM -0800, Doug
> Thompson wrote:
> > For each Chip-Select Row (csrow) there would be
> > information. I am still trying to determine if
> each
> > csrow would be in its own directory or all cwrows
> just
> > flat in the mc0, mc1, ... directories.
> >
> > Assuming each csrow is in its own directory (which
> is
> > the way I am leaning) below:
> >
> > csrow0/
> > csrow1/
> > csrow2/
> > csrow3/
> > ...
> >
> > info files in the above directories:
> >
> > memory_size
> > memory_type
> > device_type
> > edac_mode
> > ue_count
> > ce_count
> > ce_count_channel_0
> > ce_count_channel_1
> > dimm_label
> > dimm_label_channel_0
> > dimm_label_channel_1
> >
>
> Ok, thanks for the details, it makes more sense now.
> Your heirachy
> seems sane, have you implemented it to see if it
> works properly?
I began implementing first in /sys/classes and that is
when I ran into the nested class issue. I then looked
at the /sys/devices/system interface point and then
sought more information and then ASKED for RFC from
the list.
I will now use the /sys/devices/system/edac as my root
for my files and controls.
Speaking of controls, edac has them currently in
/proc/sys/mc. I have proposed to have them in
/sys/devices/system/edac/mc and friends.
My question is: Should I remove entirely my old
/proc/sys/mc sysctl tree? Or still maintain the
aliases there (which seems weird)?
If I do that, then /etc/sysctl.conf will no longer
allow for setting things up there.
Is there going to be a similiar functionality as
/etc/sysctl.conf for those items we place in sysfs, in
the future?
thanks
doug t
PS. These questions on sysfs seem a perfect food
stream for your 'HOWTO do kernel development'. Trying
to do new entries in sysfs has been a painstaking
adventure. After googling the web for info, it
definitely has been a bit thin on information on sysfs
at the level I am seeking.
>
> thanks,
>
> greg k-h
>
"If you think Education is expensive, just try Ignorance"
"Don't tell people HOW to do things, tell them WHAT you
want and they will surprise you with their ingenuity."
Gen George Patton
next prev parent reply other threads:[~2005-11-16 0:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 22:14 Doug Thompson
2005-11-14 22:31 ` Greg KH
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 [this message]
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=20051116002638.762.qmail@web50106.mail.yahoo.com \
--to=norsk5@yahoo.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.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
all inboxes | Powered by JetHome®