michaelh/zephyr
1
0
Fork 0
Code Releases Activity

clarify use of term 'context'

Browse source 
The term 'context' is vague and overloaded. Its usage for 'an execution
context' is now referred as such, in both comments and some APIs' names.
When the execution context can only be a fiber or a task (i.e. not an
ISR), it is referred to as a 'thread', again in comments and everywhere
in the code.

APIs that had their names changed:

  - nano_context_id_t is now nano_thread_id_t
  - context_self_get() is now sys_thread_self_get()
  - context_type_get() is now sys_execution_context_type_get()
  - context_custom_data_set/get() are now
    sys_thread_custom_data_set/get()

The 'context' prefix namespace does not have to be reserved by the
kernel anymore.

The Context Control Structure (CCS) data structure is now the Thread
Control Structure (TCS):

  - struct ccs is now struct tcs
  - tCCS is now tTCS

Change-Id: I7526a76c5b01e7c86333078e2d2e77c9feef5364
Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
This commit is contained in:
Benjamin Walsh 2015-08-20 11:04:01 -04:00 • committed by Anas Nashif
commit 0dcad8331b
96 changed files with 1082 additions and 1086 deletions
Download patch file Download diff file Expand all files Collapse all files

18
arch/arm/core/fault.c
View file

@ -84,7 +84,7 @@ void _FaultDump(const NANO_ESF *esf, int fault)
PR_EXC("Fault! EXC #%d, Thread: %x, instr @ %x\n",
fault,
context_self_get(),
sys_thread_self_get(),
esf->pc);
if (3 == fault) { /* hard fault */
@ -120,7 +120,7 @@ void _FaultDump(const NANO_ESF *esf, int fault)
#if (CONFIG_FAULT_DUMP == 2)
/**
*
* @brief Dump context information
* @brief Dump thread information
*
* See _FaultDump() for example.
*
@ -129,11 +129,11 @@ void _FaultDump(const NANO_ESF *esf, int fault)
* \NOMANUAL
*/
static void _FaultContextShow(const NANO_ESF *esf)
static void _FaultThreadShow(const NANO_ESF *esf)
{
PR_EXC(" Executing context ID (thread): 0x%x\n"
PR_EXC(" Executing thread ID (thread): 0x%x\n"
" Faulting instruction address: 0x%x\n",
context_self_get(),
sys_thread_self_get(),
esf->pc);
}
@ -153,7 +153,7 @@ static void _MpuFault(const NANO_ESF *esf,
{
PR_EXC("***** MPU FAULT *****\n");
_FaultContextShow(esf);
_FaultThreadShow(esf);
if (_ScbMemFaultIsStacking()) {
PR_EXC(" Stacking error\n");
@ -188,7 +188,7 @@ static void _BusFault(const NANO_ESF *esf,
{
PR_EXC("***** BUS FAULT *****\n");
_FaultContextShow(esf);
_FaultThreadShow(esf);
if (_ScbBusFaultIsStacking()) {
PR_EXC(" Stacking error\n");
@ -228,7 +228,7 @@ static void _UsageFault(const NANO_ESF *esf)
{
PR_EXC("***** USAGE FAULT *****\n");
_FaultContextShow(esf);
_FaultThreadShow(esf);
/* bits are sticky: they stack and must be reset */
if (_ScbUsageFaultIsDivByZero()) {
@ -325,7 +325,7 @@ static void _ReservedException(const NANO_ESF *esf,
*
* eg. (precise bus error escalated to hard fault):
*
* Executing context ID (thread): 0x200000dc
* Executing thread ID (thread): 0x200000dc
* Faulting instruction address: 0x000011d3
* ***** HARD FAULT *****
* Fault escalation (see below)