1. 04 Mar, 2021 1 commit
    • Pali Rohár's avatar
      Print newline after hex address in aarch64 el3_panic function · 805f22ba
      Pali Rohár authored
      
      
      Make the aarch64's el3_panic() function print a newline character after
      PC address, otherwise the output can get mangled in one line with output
      from other firmware. Here is an example of how the output of el3_panic()
      got mangled with Linux' console output:
      
          ERROR:   Unhandled External Abort received on 0x80000001 at EL3!
          ERROR:    exception reason=1 syndrome=0x92000210
          PANIC at PC : 0x0000000004027400[13438.473133] rcu: INFO: rcu_sched detected stalls on CPUs/tasks:
          [13438.479255] rcu:     1-...0: (4 ticks this GP) idle=35e/1/0x4000000000000000 softirq=146459/146459 fqs=2625
      
      The aarch32 version of this function already does this.
      Signed-off-by: default avatarPali Rohár <pali@kernel.org>
      Change-Id: I9f0d032c6cd1e2be7a1837f9c8e8244d30633993
      805f22ba
  2. 12 Feb, 2021 4 commits
  3. 11 Feb, 2021 8 commits
  4. 10 Feb, 2021 3 commits
  5. 09 Feb, 2021 5 commits
    • Manish V Badarkhe's avatar
      plat/arm: fvp: Protect GICR frames for fused/unused cores · f98630fb
      Manish V Badarkhe authored
      
      
      Currently, BLs are mapping the GIC memory region as read-write
      for all cores on boot-up.
      
      This opens up the security hole where the active core can write
      the GICR frame of fused/inactive core. To avoid this issue, disable
      the GICR frame of all inactive cores as below:
      
      1. After primary CPU boots up, map GICR region of all cores as
         read-only.
      2. After primary CPU boots up, map its GICR region as read-write
         and initialize its redistributor interface.
      3. After secondary CPU boots up, map its GICR region as read-write
         and initialize its redistributor interface.
      4. All unused/fused core's redistributor regions remain read-only and
         write attempt to such protected regions results in an exception.
      
      As mentioned above, this patch offers only the GICR memory-mapped
      region protection considering there is no facility at the GIC IP
      level to avoid writing the redistributor area.
      
      These changes are currently done in BL31 of Arm FVP and guarded under
      the flag 'FVP_GICR_REGION_PROTECTION'.
      
      As of now, this patch is tested manually as below:
      1. Disable the FVP cores (core 1, 2, 3) with core 0 as an active core.
      2. Verify data abort triggered by manually updating the ‘GICR_CTLR’
         register of core 1’s(fused) redistributor from core 0(active).
      
      Change-Id: I86c99c7b41bae137b2011cf2ac17fad0a26e776d
      Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
      f98630fb
    • Manish V Badarkhe's avatar
      doc: Build option to protect GICR frame · d30a6615
      Manish V Badarkhe authored
      
      
      Added a build option 'FVP_GICR_REGION_PROTECTION' to make
      redistributor frame of fused/unused cores as read only.
      
      Change-Id: Ie85f86e2465b93321a92a888ce8712a3144e4ccb
      Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
      d30a6615
    • Manish V Badarkhe's avatar
      plat/arm: fvp: Do not map GIC region in BL1 and BL2 · e0cea783
      Manish V Badarkhe authored
      
      
      GIC memory region is not getting used in BL1 and BL2.
      Hence avoid its mapping in BL1 and BL2 that freed some
      page table entries to map other memory regions in the
      future.
      
      Retains mapping of CCN interconnect region in BL1 and BL2
      overlapped with the GIC memory region.
      
      Change-Id: I880dd0690f94b140e59e4ff0c0d436961b9cb0a7
      Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
      e0cea783
    • Sandrine Bailleux's avatar
    • Usama Arif's avatar
      fdts: use scmi_dvfs clock index 1 for cores 4-7 · a97c390b
      Usama Arif authored
      
      
      This allows Matterhorn cores to operate at their optimal OPPs.
      Signed-off-by: default avatarUsama Arif <usama.arif@arm.com>
      Change-Id: I2e1b784da10154a1f1f65dd0e3a39213e7683116
      a97c390b
  6. 08 Feb, 2021 1 commit
  7. 05 Feb, 2021 5 commits
  8. 04 Feb, 2021 1 commit
  9. 03 Feb, 2021 8 commits
  10. 02 Feb, 2021 4 commits