1. 30 Jan, 2019 1 commit
    • Andre Przywara's avatar
      arm: turn pr_info() into pr_debug() messages · e1c7c62a
      Andre Przywara authored
      
      
      For whatever reason on ARM/arm64 machines kvmtool greets us with quite
      some elaborate messages:
        Info: Loaded kernel to 0x80080000 (18704896 bytes)
        Info: Placing fdt at 0x8fe00000 - 0x8fffffff
        Info: virtio-mmio.devices=0x200@0x10000:36
      
        Info: virtio-mmio.devices=0x200@0x10200:37
      
        Info: virtio-mmio.devices=0x200@0x10400:38
      
      This is not really useful information for the casual user, so change
      those lines to use pr_debug().
      This also fixes the long standing line ending issue for the mmio output.
      Signed-off-by: Andre Przywara's avatarAndre Przywara <andre.przywara@arm.com>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      e1c7c62a
  2. 22 Jan, 2019 2 commits
  3. 09 Oct, 2017 1 commit
  4. 09 Jun, 2017 3 commits
    • Will Deacon's avatar
      ARM: fdt: Bump CPU_NAME_MAX_LEN to avoid silly GCC warning · cc874a22
      Will Deacon authored
      
      
      GCC 7 warns about truncating the mpidr when we print the cpu_name into
      the device tree:
      
      arm/fdt.c: In function ‘setup_fdt’:
      arm/fdt.c:58:45: error: ‘%lx’ directive output may be truncated writing between 1 and 10 bytes into a region of size 7 [-Werror=format-truncation=]
         snprintf(cpu_name, CPU_NAME_MAX_LEN, "cpu@%lx", mpidr);
      
      Fix this by bumping the buffer to 15 bytes. We really only need 11 bytes,
      but GCC isn't smart enough to identify that we mask out the top buts
      of the MPIDR and the analysis just seems to be based on types.
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      cc874a22
    • Andre Przywara's avatar
      arm: use static DT phandle for the GIC · 0063d50c
      Andre Przywara authored
      
      
      As KVM supports only onc (v)GIC per guest and it's hard to imagine that
      we will ever need more than that, lets simplify the FDT generation by
      not passing that single, constant phandle around.
      Let's just reference that one global symbol from enum phandles instead.
      Acked-by: default avatarMarc Zyngier <marc.zyngier@arm.com>
      Signed-off-by: Andre Przywara's avatarAndre Przywara <andre.przywara@arm.com>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      0063d50c
    • Andre Przywara's avatar
      FDT: use static phandles · cd9a8066
      Andre Przywara authored
      
      
      The current implementation of fdt__alloc_phandle() suffers from being
      implemented in a static inline function situated in a header file.
      This will only create expected results within a single compilation
      unit.
      It seems a bit over the top to use a function to allocate phandles,
      when at the end of the day a phandle is just a unique identifier.
      To simplify things - especially with upcoming patches - we just
      introduce an enum per architecture to hold all possible phandle sources
      and use that instead of the dynamic allocation.
      Acked-by: default avatarMarc Zyngier <marc.zyngier@arm.com>
      Signed-off-by: Andre Przywara's avatarAndre Przywara <andre.przywara@arm.com>
      Signed-off-by: default avatarWill Deacon <will.deacon@arm.com>
      cd9a8066
  5. 18 Nov, 2015 3 commits
  6. 01 Jun, 2015 16 commits