1. 27 Jul, 2020 4 commits
  2. 22 Jul, 2020 3 commits
  3. 20 Jul, 2020 9 commits
  4. 10 Jul, 2020 5 commits
    • Sven Schnelle's avatar
      s390: add trace events for idle enter/exit · 6589c93f
      Sven Schnelle authored
      Helpful for debugging.
      Signed-off-by: default avatarSven Schnelle <svens@linux.ibm.com>
      Reviewed-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      6589c93f
    • Christian Borntraeger's avatar
      s390: fix comment regarding interrupts in svc · 7b7735c5
      Christian Borntraeger authored
      With the removal of the critical section cleanup, we now enter the svc
      interrupt handler with interrupts disabled.
      
      Fixes: 0b0ed657 ("s390: remove critical section cleanup from entry.S")
      Signed-off-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      7b7735c5
    • Harald Freudenberger's avatar
      s390/ap: rework crypto config info and default domain code · c8337c47
      Harald Freudenberger authored
      Rework of the QCI crypto info and how it is used.
      This is only a internal rework but does not affect the way
      how the ap bus acts with ap card and queue devices and
      domain handling.
      
      Tested on z15, z14, z12 (QCI support) and z196 (no QCI support).
      Signed-off-by: default avatarHarald Freudenberger <freude@linux.ibm.com>
      Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      c8337c47
    • David Hildenbrand's avatar
      s390/mm: don't set ARCH_KEEP_MEMBLOCK · fa49066f
      David Hildenbrand authored
      Commit 50be6345 ("s390/mm: Convert bootmem to memblock") mentions
      	"The original bootmem allocator is getting replaced by memblock. To
      	cover the needs of the s390 kdump implementation the physical
      	memory list is used."
      
      As we can now reference "physmem" managed in the memblock allocator after
      init even without ARCH_KEEP_MEMBLOCK, and s390x does no longer need
      other memblock metadata after boot (esp., the zcore memmap device that used
      it got removed), we can stop setting ARCH_KEEP_MEMBLOCK.
      
      With this change, we no longer create memblocks for standby/hotplugged
      memory (added via add_memory()) and free up memblock metadata (except
      physmem) after boot.
      
      Cc: Vasily Gorbik <gor@linux.ibm.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Philipp Rudo <prudo@linux.ibm.com>
      Cc: Mike Rapoport <rppt@linux.ibm.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Message-Id: <20200701141830.18749-3-david@redhat.com>
      Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      fa49066f
    • David Hildenbrand's avatar
      mm/memblock: expose only miminal interface to add/walk physmem · 77649905
      David Hildenbrand authored
      "physmem" in the memblock allocator is somewhat weird: it's not actually
      used for allocation, it's simply information collected during boot, which
      describes the unmodified physical memory map at boot time, without any
      standby/hotplugged memory. It's only used on s390 and is currently the
      only reason s390 keeps using CONFIG_ARCH_KEEP_MEMBLOCK.
      
      Physmem isn't numa aware and current users don't specify any flags. Let's
      hide it from the user, exposing only for_each_physmem(), and simplify. The
      interface for physmem is now really minimalistic:
      - memblock_physmem_add() to add ranges
      - for_each_physmem() / __next_physmem_range() to walk physmem ranges
      
      Don't place it into an __init section and don't discard it without
      CONFIG_ARCH_KEEP_MEMBLOCK. As we're reusing __next_mem_range(), remove
      the __meminit notifier to avoid section mismatch warnings once
      CONFIG_ARCH_KEEP_MEMBLOCK is no longer used with
      CONFIG_HAVE_MEMBLOCK_PHYS_MAP.
      
      While fixing up the documentation, sneak in some related cleanups. We can
      stop setting CONFIG_ARCH_KEEP_MEMBLOCK for s390 next.
      
      Cc: Vasily Gorbik <gor@linux.ibm.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Mike Rapoport <rppt@linux.ibm.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Reviewed-by: default avatarMike Rapoport <rppt@linux.ibm.com>
      Message-Id: <20200701141830.18749-2-david@redhat.com>
      Signed-off-by: default avatarHeiko Carstens <hca@linux.ibm.com>
      77649905
  5. 03 Jul, 2020 9 commits
  6. 01 Jul, 2020 3 commits
    • Oscar Carter's avatar
      s390/tty3270: remove function callback casts · 5cdfbdce
      Oscar Carter authored
      In an effort to enable -Wcast-function-type in the top-level Makefile to
      support Control Flow Integrity builds, remove all the function callback
      casts.
      
      To do this modify the function prototypes accordingly.
      Signed-off-by: default avatarOscar Carter <oscar.carter@gmx.com>
      Message-Id: <20200627125417.18887-1-oscar.carter@gmx.com>
      Reviewed-by: default avatarKees Cook <keescook@chromium.org>
      [heiko.carstens@de.ibm.com: coding style changes]
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      5cdfbdce
    • David Hildenbrand's avatar
      s390/vmem: get rid of memory segment list · f05f62d0
      David Hildenbrand authored
      I can't come up with a satisfying reason why we still need the memory
      segment list. We used to represent in the list:
      - boot memory
      - standby memory added via add_memory()
      - loaded dcss segments
      
      When loading/unloading dcss segments, we already track them in a
      separate list and check for overlaps
      (arch/s390/mm/extmem.c:segment_overlaps_others()) when loading segments.
      
      The overlap check was introduced for some segments in
      commit b2300b9e ("[S390] dcssblk: add >2G DCSSs support and stacked
      contiguous DCSSs support.")
      and was extended to cover all dcss segments in
      commit ca571146 ("s390/extmem: remove code for 31 bit addressing
      mode").
      
      Although I doubt that overlaps with boot memory and standby memory
      are relevant, let's reshuffle the checks in load_segment() to request
      the resource first. This will bail out in case we have overlaps with
      other resources (esp. boot memory and standby memory). The order
      is now different compared to segment_unload() and segment_unload(), but
      that should not matter.
      
      This smells like a leftover from ancient times, let's get rid of it. We
      can now convert vmem_remove_mapping() into a void function - everybody
      ignored the return value already.
      
      Cc: Vasily Gorbik <gor@linux.ibm.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Andrew Morton <akpm@linux-foundation.org>
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Message-Id: <20200625150029.45019-1-david@redhat.com>
      Reviewed-by: default avatarGerald Schaefer <gerald.schaefer@de.ibm.com>
      Tested-by: Gerald Schaefer <gerald.schaefer@de.ibm.com> [DCSS]
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      f05f62d0
    • Sven Schnelle's avatar
      s390/stp: allow group and users to read stp sysfs files · 66a049b7
      Sven Schnelle authored
      There are no secrets in these files, so allow all users
      to read it.
      Signed-off-by: default avatarSven Schnelle <svens@linux.ibm.com>
      Acked-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      Signed-off-by: default avatarHeiko Carstens <heiko.carstens@de.ibm.com>
      66a049b7
  7. 29 Jun, 2020 7 commits