Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training


Context Save/Restore in Interrupts

Posted by Nobody/Anonymous on July 6, 2005
Am I getting this right?

The reason that the context has to be saved and then restored is that because the scheduler can not yield in the regular way while in interrupt context (as we assume there are no nested interrupts, and the yield is done through software interrupt).
So we restore the context at the end of every interrupt; If a context switch was performed somewhere along the ISR, the ISR assembly wrapper will just complete the action usually done by the software interrupt used for yield.
Otherwise, the context restore will do nothing.

What did I get wrong there? :)

RE: Context Save/Restore in Interrupts

Posted by Richard on July 6, 2005
Basically, but it is not always necessary to save and restore the context each ISR, depending on the ISR, but also depending on the processor and tools.

Some times it is more efficient to save everything on entry and exist, sometimes to only save when needed at the cost of some duplication (some registers getting saved twice). Also some compilers make this easier than others.

Which port are you using? (processor and tools) Your comment about wrapper code narrows it down, but which one?


RE: Context Save/Restore in Interrupts

Posted by Nobody/Anonymous on July 6, 2005
I'm using the SAM7 IAR port.
I see when there is no reason for wrapping - essentially, when you're not doing anything that might indirectly yield, such as locking a resource, writing to a queue, etc...

BTW, this will be a very good place to admit you for the excellent, excellent work you've done!

[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]

Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.

Free TCP/IP and file system demos for the RTOS

Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists