| To: | linux-mips@linux-mips.org |
|---|---|
| Subject: | Is r25 saved across syscalls? |
| From: | Rich Felker <dalias@aerifal.cx> |
| Date: | Sun, 9 Sep 2012 15:30:08 -0400 |
| List-archive: | <http://www.linux-mips.org/archives/linux-mips/> |
| List-help: | <mailto:ecartis@linux-mips.org?Subject=help> |
| List-id: | linux-mips <linux-mips.eddie.linux-mips.org> |
| List-owner: | <mailto:ralf@linux-mips.org> |
| List-post: | <mailto:linux-mips@linux-mips.org> |
| List-software: | Ecartis version 1.0.0 |
| List-subscribe: | <mailto:ecartis@linux-mips.org?subject=subscribe%20linux-mips> |
| List-unsubscribe: | <mailto:ecartis@linux-mips.org?subject=unsubscribe%20linux-mips> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
Hi all, The kernel syscall entry/exit code seems to always save and restore r25. Is this stable/documented behavior I can rely on? If there's a reason it _needs_ to be preserved, knowing that would help convince me it's safe to assume it will always be done. The intended usage is to be able to make syscalls (where the syscall # is not a constant that could be loaded with lwi) without a stack frame, as in "move $2,$25 ; syscall". Rich |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH v3 2/3] bcma: add GPIO driver for SoCs, Hauke Mehrtens |
|---|---|
| Next by Date: | [PATCH v2 0/3] MIPS: JZ4740: Move PWM driver to PWM framework, Thierry Reding |
| Previous by Thread: | Re: MIPS: Fix build error with modern GCC for non-Cavium., Maciej W. Rozycki |
| Next by Thread: | Re: Is r25 saved across syscalls?, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |