mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Doug Thompson <norsk5@yahoo.com>
To: greg@kroah.com
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: [RFC] EDAC a new sysfs 'subsystem' under /sys/devices
Date: Tue, 22 Nov 2005 15:57:44 -0800 (PST)	[thread overview]
Message-ID: <20051122235744.15404.qmail@web50110.mail.yahoo.com> (raw)

EDAC is for detecting and logging memory ECC, PCI
Parity and (future) other hardware errors.

In my process of getting edac ready for kernel
submission:

I have been exploring mechanisms for placing EDAC
controls and attribute files into sysfs for a few days
now.

In the process, I "discovered" how sysfs subystems are
currently used. I have determined that EDAC itself
should be a subsystem, since more than one type of
EDAC device can be created.

I made a copy of drivers/base/sys.c to a new file,
drivers/base/edac.c (and corresponding .h file) and
refactored it to become a 'edacdev' subsystem.

I have mounted edac to: /sys/devices/edac because the
/sys/device/system subsystem is not exported (at the
moment. I suppose that could be changed). 

I now have:

/sys/devices/edac/mc/mc0/csrow0 kobjects working and
am adding attribute files to their respective
kobjects.

My RFC is:

Should I leave edac under /sys/devices OR refactor
drivers/base/sys.c and export the "system" subsystem
and mount edac under /sys/devices/system? 

Another RFC is:

Should EDAC really have a "new" subsystem in the
kernel?  (I believe it fits bets, but am looking for
alternatives)

It requires a new drivers/base/edac.c (and .h file +
plumbing).  I would like to see that, as it really
works nicely. The EDAC module currently in the -mm
tree will depend  on it, in order to implement the
requested sysfs features. (Other options are possible
I suppose)

The only problem I ran into was that I needed further
subdirectories under 'mc/mc0', and I had to resort to
using kobject_register() since the subsystem didn't
have methods for such creation. Yet that code now
works nicely.


I suppose I am looking for verification of the
direction I am progressing in.

Thanks for any input

doug t




"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


             reply	other threads:[~2005-11-22 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22 23:57 Doug Thompson [this message]
2005-11-28 20:56 ` Greg KH
2005-11-28 21:42   ` Doug Thompson

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=20051122235744.15404.qmail@web50110.mail.yahoo.com \
    --to=norsk5@yahoo.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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®