From: Ralf Baechle <ralf@linux-mips.org>
To: zhuzhenhua <zzh.hust@gmail.com>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: does the SAVE_ALL nesting in kernel?
Date: Wed, 12 Sep 2007 17:53:30 +0100 [thread overview]
Message-ID: <20070912165330.GH4571@linux-mips.org> (raw)
In-Reply-To: <50c9a2250709111921g1b49cb0du7f97ebb3e1fb7d07@mail.gmail.com>
On Wed, Sep 12, 2007 at 10:21:53AM +0800, zhuzhenhua wrote:
> i have a mips board, and the SDRAM speed(bus clock) is not too
> fast.
> so i want change the SAVE_ALL and RESTORE_ALL to use
> internal-ram(high speed).
> i just wonder whether the SAVE_ALL netsting in kernel for mips
> arch?
> if not, i think maybe 1k byte for SAVE_ALL is enough( 32regs
> X4, and some cp0_regs).
> but if the SAVE_ALL nesting, maybe i need to keep a stack in
> internal-ram.
> thanks for any hints．
Nesting works but due to the use of k0/k1 you need to ensure SAVE_ALL is
only invoked with interrupts disabled.
Ralf
prev parent reply other threads:[~2007-09-12 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 2:21 does the SAVE_ALL nesting in kernel? zhuzhenhua
2007-09-12 3:17 ` Dajie Tan
2007-09-12 3:30 ` Dajie Tan
2007-09-12 9:11 ` Kevin D. Kissell
2007-09-13 7:00 ` zhuzhenhua
2007-09-12 16:53 ` Ralf Baechle [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=20070912165330.GH4571@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=zzh.hust@gmail.com \
/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