linux-kernel - [rfc] exposing MMR's of on-chip peripherals for debugging purposes

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-next>] [day] [month] [year] [list]

Message-ID: <8bd0f97a0801280216x56d52028s2ea247dd969e85e2@mail.gmail.com>
Date:	Mon, 28 Jan 2008 05:16:20 -0500
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Cc:	"Bryan Wu" <cooloney.lkml@...il.com>
Subject: [rfc] exposing MMR's of on-chip peripherals for debugging purposes

we have guys who maintain xml descriptions of all Blackfin processors.
 these include an exhaustive list of all the peripherals and their
MMRs.  for example, there is an element that binds the address, the
MMR name (as described in the processor's hardware manual), the bit
size of it, and all those fun details.  i feed these xml files through
an xsl to generate a C file that populates /sys/kernel/debug/blackfin/
by using the standard debugfs functions.  so when i'm debugging the
watchdog driver, i can simply go into
/sys/kernel/debug/blackfin/watchdog/ and see the watchdog-specific
MMRs and cat/echo them on the fly.  it's been quite handy and feedback
from customers/developers is that it's nicely filled a small void in
the development process.

the trouble is that this file currently weighs in at ~1.8 megs.  this
is because it contains all the information for all Blackfin processors
we support (which currently, is about ~23 variants).  it's only going
to get bigger as we support more.  Bryan cringes at the thought of
submitting it to LKML :).  so i'm fishing around for alternatives ...
the code was originally developed against 2.6.21, so UIO was not a
possibility.  i'm still not sure if it is ... i'd have to research it
a bit more and play with things.

any pointers ?
-mike
--
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/