⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 cpu.h

📁 RTEMS (Real-Time Executive for Multiprocessor Systems) is a free open source real-time operating sys
💻 H
📖 第 1 页 / 共 3 页
字号:
  _CPU_MSR_SET(msr);}  void BSP_panic(char *);#define _CPU_ISR_install_vector(irq, new, old) \   {BSP_panic("_CPU_ISR_install_vector called\n");}/* Context handler macros *//* *  Initialize the context to a state suitable for starting a *  task after a context restore operation.  Generally, this *  involves: * *     - setting a starting address *     - preparing the stack *     - preparing the stack and frame pointers *     - setting the proper interrupt level in the context *     - initializing the floating point context * *  This routine generally does not set any unnecessary register *  in the context.  The state of the "general data" registers is *  undefined at task start time. * *  NOTE:  Implemented as a subroutine for the SPARC port. */void _CPU_Context_Initialize(  Context_Control  *the_context,  unsigned32       *stack_base,  unsigned32        size,  unsigned32        new_level,  void             *entry_point,  boolean           is_fp);/* *  This routine is responsible for somehow restarting the currently *  executing task.  If you are lucky, then all that is necessary *  is restoring the context.  Otherwise, there will need to be *  a special assembly routine which does something special in this *  case.  Context_Restore should work most of the time.  It will *  not work if restarting self conflicts with the stack frame *  assumptions of restoring a context. */#define _CPU_Context_Restart_self( _the_context ) \   _CPU_Context_restore( (_the_context) );/* *  The purpose of this macro is to allow the initial pointer into *  a floating point context area (used to save the floating point *  context) to be at an arbitrary place in the floating point *  context area. * *  This is necessary because some FP units are designed to have *  their context saved as a stack which grows into lower addresses. *  Other FP units can be saved by simply moving registers into offsets *  from the base of the context area.  Finally some FP units provide *  a "dump context" instruction which could fill in from high to low *  or low to high based on the whim of the CPU designers. */#define _CPU_Context_Fp_start( _base, _offset ) \   ( (void *) _Addresses_Add_offset( (_base), (_offset) ) )/* *  This routine initializes the FP context area passed to it to. *  There are a few standard ways in which to initialize the *  floating point context.  The code included for this macro assumes *  that this is a CPU in which a "initial" FP context was saved into *  _CPU_Null_fp_context and it simply copies it to the destination *  context passed to it. * *  Other models include (1) not doing anything, and (2) putting *  a "null FP status word" in the correct place in the FP context. */#define _CPU_Context_Initialize_fp( _destination ) \  { \   ((Context_Control_fp *) *((void **) _destination))->fpscr = PPC_INIT_FPSCR; \  }/* end of Context handler macros *//* Fatal Error manager macros *//* *  This routine copies _error into a known place -- typically a stack *  location or a register, optionally disables interrupts, and *  halts/stops the CPU. */void _BSP_Fatal_error(unsigned int);#define _CPU_Fatal_halt( _error ) \  _BSP_Fatal_error(_error)/* end of Fatal Error manager macros *//* Bitfield handler macros *//* *  This routine sets _output to the bit number of the first bit *  set in _value.  _value is of CPU dependent type Priority_Bit_map_control. *  This type may be either 16 or 32 bits wide although only the 16 *  least significant bits will be used. * *  There are a number of variables in using a "find first bit" type *  instruction. * *    (1) What happens when run on a value of zero? *    (2) Bits may be numbered from MSB to LSB or vice-versa. *    (3) The numbering may be zero or one based. *    (4) The "find first bit" instruction may search from MSB or LSB. * *  RTEMS guarantees that (1) will never happen so it is not a concern. *  (2),(3), (4) are handled by the macros _CPU_Priority_mask() and *  _CPU_Priority_Bits_index().  These three form a set of routines *  which must logically operate together.  Bits in the _value are *  set and cleared based on masks built by _CPU_Priority_mask(). *  The basic major and minor values calculated by _Priority_Major() *  and _Priority_Minor() are "massaged" by _CPU_Priority_Bits_index() *  to properly range between the values returned by the "find first bit" *  instruction.  This makes it possible for _Priority_Get_highest() to *  calculate the major and directly index into the minor table. *  This mapping is necessary to ensure that 0 (a high priority major/minor) *  is the first bit found. * *  This entire "find first bit" and mapping process depends heavily *  on the manner in which a priority is broken into a major and minor *  components with the major being the 4 MSB of a priority and minor *  the 4 LSB.  Thus (0 << 4) + 0 corresponds to priority 0 -- the highest *  priority.  And (15 << 4) + 14 corresponds to priority 254 -- the next *  to the lowest priority. * *  If your CPU does not have a "find first bit" instruction, then *  there are ways to make do without it.  Here are a handful of ways *  to implement this in software: * *    - a series of 16 bit test instructions *    - a "binary search using if's" *    - _number = 0 *      if _value > 0x00ff *        _value >>=8 *        _number = 8; * *      if _value > 0x0000f *        _value >=8 *        _number += 4 * *      _number += bit_set_table[ _value ] * *    where bit_set_table[ 16 ] has values which indicate the first *      bit set */#define _CPU_Bitfield_Find_first_bit( _value, _output ) \  { \    asm volatile ("cntlzw %0, %1" : "=r" ((_output)), "=r" ((_value)) : \		  "1" ((_value))); \  }/* end of Bitfield handler macros *//* *  This routine builds the mask which corresponds to the bit fields *  as searched by _CPU_Bitfield_Find_first_bit().  See the discussion *  for that routine. */#define _CPU_Priority_Mask( _bit_number ) \  ( 0x80000000 >> (_bit_number) )/* *  This routine translates the bit numbers returned by *  _CPU_Bitfield_Find_first_bit() into something suitable for use as *  a major or minor component of a priority.  See the discussion *  for that routine. */#define _CPU_Priority_bits_index( _priority ) \  (_priority)/* end of Priority handler macros *//* variables */extern const unsigned32 _CPU_msrs[4];/* functions *//* *  _CPU_Initialize * *  This routine performs CPU dependent initialization. * *  Until all new-exception processing BSPs have fixed *  PR288, we let the good BSPs pass * *  PPC_BSP_HAS_FIXED_PR288 * *  in SPRG0 and let _CPU_Initialize assert this. */#define PPC_BSP_HAS_FIXED_PR288	0x600dbabevoid _CPU_Initialize(  rtems_cpu_table  *cpu_table,  void            (*thread_dispatch));/* *  _CPU_Install_interrupt_stack * *  This routine installs the hardware interrupt stack pointer. * *  NOTE:  It need only be provided if CPU_HAS_HARDWARE_INTERRUPT_STACK *         is TRUE. */void _CPU_Install_interrupt_stack( void );/* *  _CPU_Context_switch * *  This routine switches from the run context to the heir context. */void _CPU_Context_switch(  Context_Control  *run,  Context_Control  *heir);/* *  _CPU_Context_restore * *  This routine is generallu used only to restart self in an *  efficient manner.  It may simply be a label in _CPU_Context_switch. * *  NOTE: May be unnecessary to reload some registers. */void _CPU_Context_restore(  Context_Control *new_context);/* *  _CPU_Context_save_fp * *  This routine saves the floating point context passed to it. */void _CPU_Context_save_fp(  void **fp_context_ptr);/* *  _CPU_Context_restore_fp * *  This routine restores the floating point context passed to it. */void _CPU_Context_restore_fp(  void **fp_context_ptr);void _CPU_Fatal_error(  unsigned32 _error);/*  The following routine swaps the endian format of an unsigned int. *  It must be static because it is referenced indirectly. * *  This version will work on any processor, but if there is a better *  way for your CPU PLEASE use it.  The most common way to do this is to: * *     swap least significant two bytes with 16-bit rotate *     swap upper and lower 16-bits *     swap most significant two bytes with 16-bit rotate * *  Some CPUs have special instructions which swap a 32-bit quantity in *  a single instruction (e.g. i486).  It is probably best to avoid *  an "endian swapping control bit" in the CPU.  One good reason is *  that interrupts would probably have to be disabled to insure that *  an interrupt does not try to access the same "chunk" with the wrong *  endian.  Another good reason is that on some CPUs, the endian bit *  endianness for ALL fetches -- both code and data -- so the code *  will be fetched incorrectly. */ static inline unsigned int CPU_swap_u32(  unsigned int value){  unsigned32 swapped;   asm volatile("rlwimi %0,%1,8,24,31;"	       "rlwimi %0,%1,24,16,23;"	       "rlwimi %0,%1,8,8,15;"	       "rlwimi %0,%1,24,0,7;" :	       "=&r" ((swapped)) : "r" ((value)));  return( swapped );}#define CPU_swap_u16( value ) \  (((value&0xff) << 8) | ((value >> 8)&0xff))#endif /* ndef ASM */#ifdef __cplusplus}#endif#endif

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -