Changeset 362782e in rtems-libbsd


Ignore:
Timestamp:
Apr 16, 2012, 10:43:49 AM (7 years ago)
Author:
Sebastian Huber <sebastian.huber@…>
Branches:
4.11, fd86c091b97759106da7355ce1dd81ebe030e285, freebsd-9.3, f020f08430150c1656a0ad0a1de13699db9b980b
Children:
459afb1
Parents:
8a4f070
Message:

Explain why we need the interrupt server

File:
1 edited

Legend:

Unmodified
Added
Removed
  • libbsd.txt

    r8a4f070 r362782e  
    6868
    6969* linker section issues: I have undefined symbols for
    70   _bsd__start_set_sysinit_set and _bsd__stop_set_sysinit_set.
     70  `_bsd__start_set_sysinit_set` and `_bsd__stop_set_sysinit_set`.
    7171  Is this the only type of new section magic?  What about the old sysctl_set?
    7272  I added this to my linkcmds. 
     
    8181
    8282----
     83
     84* Why is the interrupt server used?  The BSD interrupt handlers can block on
     85synchronization primitives like mutexes.  This is in contrast to RTEMS
     86interrupt service routines.  The BSPs using the generic interrupt support must
     87implement the `bsp_interrupt_vector_enable()` and
     88`bsp_interrupt_vector_disable()` routines.  They normally enable/disable a
     89particular interrupt source at the interrupt controller.  This can be used to
     90implement the interrupt server.  The interrupt server is a task that wakes-up
     91in case an associated interrupt happens.  The interrupt source is disabled in
     92a generic interrupt handler that wakes-up the interrupt server task.   Once the
     93postponed interrupt processing is performed in the interrupt server the
     94interrupt source is enabled again.
    8395
    8496* Convert all BSP linkcmds to use a linkcmds.base so the sections are
Note: See TracChangeset for help on using the changeset viewer.