| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Close #2401.
|
|
|
|
| |
CPU_STRUCTURE_ALIGNMENT.
|
|
|
|
|
|
|
|
| |
Some/many Cortex-A cores have data cache line length 64 bytes and maximum
value has to be used for system structures alignment.
Updates #2782
Updates #2783
|
|
|
|
|
|
|
|
|
|
|
| |
base access.
The main reason for inclusion of minimum hypervisor related defines
is that current ARM boards firmware and loaders (U-boot for example)
start loaded operating system kernel in HYP mode to allow it take
control of virtualization (Linux/KVM for example).
Updates #2783
|
|
|
|
|
|
|
|
|
| |
Only use CPU_Per_CPU_control if it contains at least one filed. In GNU
C empty structures have a size of zero. In C++ structures have a
non-zero size. In case CPU_PER_CPU_CONTROL_SIZE is defined to zero,
then this structure is not used anymore.
Close #2789.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We must not load registers (e.g. PSR) from the heir context area before
the heir stopped execution.
With this patch the write to PSR is divided into two steps. We first update
the current window pointer and then we restore the status registers and
enable traps. This allows us to move the first write to PSR to be before
the write to WIM, as there is now no risk that we get an interrupt where
the CWP and WIM would be inconsistent. We only need to make sure that we
do not use any of the non-global registers or instructions that affects
CWP for three instructions after the write.
In the earlier code the non-global %o1 register was used right after the
write to PSR, which required the use of three nop:s.
Close #2472.
|
|
|
|
| |
Close #2470.
|
| |
|
| |
|
|
|
|
| |
Fixes link failure when linking Ada programs on the raspberry pi
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The e500v1 has no support for the ATB.
Update #2369.
|
|
|
|
|
|
| |
The mftb is not available on Book E processors. Use SPR 268 instead.
Close #2369.
|
| |
|
|
|
|
|
| |
Drop the <rtems/score/percpu.h> include since this file exposes a lot of
implementation details.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The SPARC ABI is a bit special with respect to the floating point context.
The complete floating point context is volatile. Thus from an ABI point
of view nothing needs to be saved and restored during a context switch.
Instead the floating point context must be saved and restored during
interrupt processing. Historically the deferred floating point switch is
used for SPARC and the complete floating point context is saved and
restored during a context switch to the new floating point unit owner.
This is a bit dangerous since post-switch actions (e.g. signal handlers)
and context switch extensions may silently corrupt the floating point
context. The floating point unit is disabled for interrupt handlers.
Thus in case an interrupt handler uses the floating point unit then this
will result in a trap.
On SMP configurations the deferred floating point switch is not
supported in principle. So use here a safe floating point support. Safe
means that the volatile floating point context is saved and restored
around a thread dispatch issued during interrupt processing. Thus
post-switch actions and context switch extensions may safely use the
floating point unit.
Update #2270.
|
|
|
|
|
|
|
|
| |
Store the floating-point unit property in the thread control block
regardless of the CPU_HARDWARE_FP and CPU_SOFTWARE_FP settings. Make
sure the floating-point unit is only enabled for the corresponding
multilibs. This helps targets which have a volatile only floating point
context like SPARC for example.
|
|
|
|
| |
Update #2270.
|
|
|
|
|
|
|
| |
The FP context save/restore makes only sense in the context of FP
threads.
Update #2270.
|
|
|
|
| |
Update #2270.
|
|
|
|
|
|
|
| |
Write the pattern only once to the entry register window and the
floating point registers.
Update #2270.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Implement _CPU_Context_validate() and _CPU_Context_volatile_clobber().
Update #2270.
|
|
|
|
| |
closes 2326.
|
|
|
|
|
|
|
|
|
|
|
| |
The stack pointer must be aligned on 8 byte boundary on ARM, so the size of
the exception frame must be a multiple of 8 bytes. Otherwise we might/will
get an alignment fault, when executing code in the data abort handler for
example.
Close #2318.
Signed-off-by: Daniel Krueger <daniel.krueger@systec-electronic.com>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #2304
|
|
|
|
| |
These were remnants of pre-Doxygen comment style.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
4e3d9a4d6c76fba8e31138d503f736405dafc213 broke or1k, cpuatomic.h has to
be added to all architectures.
|
| |
|
|
|
|
|
|
|
|
| |
In _ARMV4_Exception_fiq_default, set the F bit of the SPSR so that when
it gets loaded back to the CPSR in save_more_context it won't re-enable
the FIQs.
Tested on a TMS570LS3137.
|
|
|
|
|
| |
The sparc64 port had some incorrect copyright notices affixed to
source code files.
|
|
|
|
|
|
|
|
| |
Closes #2148
Fix suggested in above ticket. On examination, the assembly
appears to be clearing the DISPATCH_NEEDED flag before jumping
to _Thread_Dispatch.
|
|
|
|
| |
Update #2268.
|
| |
|
| |
|