linux-kernel - Re: [PATCH 1/4] Blackfin: arch patch for 2.6.18

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

Message-ID: <8bd0f97a0609221858w442b9aeagcff312d2220f70c6@mail.gmail.com>
Date:	Fri, 22 Sep 2006 21:58:27 -0400
From:	"Mike Frysinger" <vapier.adi@...il.com>
To:	"Roland Dreier" <rdreier@...co.com>
Cc:	Randy.Dunlap <rdunlap@...otime.net>, "Arnd Bergmann" <arnd@...db.de>, 
	"Luke Yang" <luke.adi@...il.com>, linux-kernel@...r.kernel.org, 
	"Andrew Morton" <akpm@...l.org>
Subject: Re: [PATCH 1/4] Blackfin: arch patch for 2.6.18

On 9/22/06, Roland Dreier <rdreier@...co.com> wrote:
>  > > > +static char *cplb_print_entry(char *buf, int type)
>
>  > examples of acceptable interfaces?
>
> I don't know exactly what a CPLB is, but it looks like this file is
> something debugging-related.  So stick it in debugfs?

a CPLB is a blackfinisim for handling cache ... it stands for Cache
Protection Lookaside Buffer

and yes, our proc file for displaying the current software copies of
the data cplb and instruction cplb tables would probably be better
implemented via debugfs as there is no real upper limit on how big the
table can grow ...
-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/