Skip to content
  1. Dec 13, 2018
  2. Dec 11, 2018
  3. Dec 10, 2018
  4. Dec 05, 2018
  5. Nov 29, 2018
    • John Tsichritzis's avatar
      Make topology.h macros more readable · 941fab43
      John Tsichritzis authored and Sandrine Bailleux's avatar Sandrine Bailleux committed
      
      
      The three parts of the "for" loops are more readable than before. The
      way they are written now, it is clear which are the initial and final
      values of the loop controlling variables.
      
      Also, parentheses were added only to those macro parameters that can
      receive expressions as arguments. E.g. in for_each_cpu(cpu), "cpu" must
      receive a variable name, it cannot receive an expression. So there was
      no reason to clutter the macro body with unnecessary parentheses
      wherever "cpu" parameter appears. Parentheses were added only around
      those parameters that might receive expressions.
      
      The parameters in for_each_cpu_in_power_domain were swapped. This was
      done for consistency with the other two macros. Thus, the first
      parameter is always the iterating variable, in all macros.
      
      Change-Id: I18831237840e9cfa738a48dbe7f1ec449c89f7af
      Signed-off-by: default avatarJohn Tsichritzis <john.tsichritzis@arm.com>
      941fab43
  6. Nov 27, 2018
  7. Nov 26, 2018
  8. Nov 20, 2018
  9. Nov 16, 2018
  10. Nov 07, 2018
  11. Nov 06, 2018
  12. Oct 31, 2018
  13. Oct 30, 2018
  14. Oct 29, 2018
  15. Oct 25, 2018
    • Sandrine Bailleux's avatar
      Disable hardware alignment checking · aef556a8
      Sandrine Bailleux authored
      
      
      At the moment, alignment fault checking is always enabled in TF-A
      Tests (by setting the HSCTLR/SCTLR.A bit). Thus, for every instruction
      that loads or stores one or more registers, the hardware checks that
      the address being accessed is properly aligned to the size of the data
      element(s) being accessed. If this check fails it causes an alignment
      fault, which is taken as a data abort exception.
      
      However, the compiler is currently unaware that it must not emit load
      and store instructions resulting in unaligned accesses because we do
      not compile the source code with -mstrict-align (AArch64) /
      -mno-unaligned-access (AArch32). Because of this, we might get some
      unexpected alignment faults.
      
      We could request the compiler to align all data accesses but whether
      this gives us any performance benefit is dependent on the
      microarchitecture. Thus, it is simpler to just disable hardware
      alignment checking and let the compiler make the call.
      
      Change-Id: I6ef4afb09e0f87c8462a968da1ca2192ee075b40
      Signed-off-by: Sandrine Bailleux's avatarSandrine Bailleux <sandrine.bailleux@arm.com>
      aef556a8
Loading