linux-kernel - Re: sysfs for my chips

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Fri, 11 Oct 2013 20:06:40 +1100
From:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	Greg KH <gregkh@...uxfoundation.org>, Tejun Heo <tj@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: sysfs for my chips

On Fri, 2013-10-11 at 08:52 +0200, Geert Uytterhoeven wrote:
> > Not sure what you mean .... create a linux bus type with devices on
> > it ?
> 
> Yes, that's what I meant.
> 
> >From the nodes on that bus you can have symlinks in sysfs to e.g. the CPUs
> in the rest of the sysfs tree.
> 
> It's a bit like smbus/i2c connecting various peripherals that may also be
> connected in some other way (e.g. media devices).

It's fairly overkill though ... we don't really plan to expose much of
these things to Linux anyway, it's mostly buried in firmware, I just
want scom access to userspace for debug/diagnostics.

I don't want it in debugfs however because we might want some "health
monitoring" daemon running in userspace that uses it to check some of
the built-in CE statistics etc... in the various chips and handle some
of the repair work. I prefer having that stuff in userspace (it's fairly
complex) than in firmware but it will get all the data it needs from the
device-tree, there's no point trying to reproduce the whole chip
hierarchy and sub hierarchy in Linux.

Cheers,
Ben.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/