Messages in this thread | | | Date | Mon, 14 Nov 2005 19:30:26 -0500 | From | Dave Jones <> | Subject | Re: [RFC] EDAC and the sysfs |
| |
On Mon, Nov 14, 2005 at 02:31:05PM -0800, Greg Kroah-Hartman wrote: > 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?
Probably the same reason we don't have the cpufreq (for eg) stuff under /sys/firmware. Because it's poking hardware, not manipulating firmware.
/sys/devices/system makes a lot more sense, as thats where the cpu level machine check stuff is (amongst other similar things).
> > 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?)
Reports hardware events read from chipset specific registers. Similar to /sys/devices/system/machinecheck/, but from chipset instead of CPU. (That's grossly simplified, but hopefully gets the idea across).
Dave
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |