From: Tom Rini <trini@kernel.crashing.org>
To: Dave Johnson <davejohnson_hifi@yahoo.com>
Cc: cort@fsmlabs.com, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.linuxppc.org
Subject: Re: Using 8 Instruction and Data BAT registers in 82xx
Date: Tue, 27 Jan 2004 10:18:58 -0700 [thread overview]
Message-ID: <20040127171858.GG32525@stop.crashing.org> (raw)
In-Reply-To: <20040126182941.50687.qmail@web21405.mail.yahoo.com>
On Mon, Jan 26, 2004 at 10:29:41AM -0800, Dave Johnson wrote:
>
> Hi All:
> As there are 8 data and Instruction BAT registers in
> some 82xx flavors, and Cort has posted a patch to ADD
> these registers
> (http://www.ussg.iu.edu/hypermail/linux/kernel/0209.1/0871.html)
> I was wondering if anyone has any idea how to use
> these addistional BAT regs be used?? Perhaps for new
> processes and threads, etc.
Step one would be to audit the usages of the 8_BATS feature to ensure
that they'll be fine if invoked on an 82xx with 8 BATS. It's almost
certainly going to be true, but should still be done.
Step two would be to distinguish the 82xx's with 8 BATs from the ones
that don't. I don't know if these have a different PVR, but I hope they
do, otherwise it'll be harder (but not impossible certainly) to.
Finally, as you've probably surmised, all that we do with these
additional BATs is to clear them out. It could be possible to extend
io_block_mapping to make use of these additional BATs (and
v_mapped_by_bats/p_mapped_by_bats, etc).
Trying to do processes and/or threads (i.e. userland stuff) becomes a
giant pain (per-context BAT mappings have to be tracked), there's lots
of security implications to keep in mind, and of course the overhead of
doing all of this will probably cancel out any speed gain you would have
otherwise gotten.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-01-27 22:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 18:29 Using 8 Instruction and Data BAT registers in 82xx Dave Johnson
2004-01-27 17:18 ` Tom Rini [this message]
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=20040127171858.GG32525@stop.crashing.org \
--to=trini@kernel.crashing.org \
--cc=cort@fsmlabs.com \
--cc=davejohnson_hifi@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.linuxppc.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