1. 13 Jul, 2018 1 commit
  2. 17 May, 2018 1 commit
  3. 14 Mar, 2018 3 commits
  4. 09 Mar, 2018 1 commit
  5. 26 Jan, 2018 4 commits
  6. 24 Jan, 2018 1 commit
  7. 20 Jan, 2018 1 commit
  8. 16 Jan, 2018 1 commit
  9. 24 Nov, 2017 2 commits
    • Greg Kroah-Hartman's avatar
      s390: include: Remove redundant license text · 94bf2f28
      Greg Kroah-Hartman authored
      
      
      Now that the SPDX tag is in all arch/s390/include/ files, that
      identifies the license in a specific and legally-defined manner.  So the
      extra GPL text wording can be removed as it is no longer needed at all.
      
      This is done on a quest to remove the 700+ different ways that files in
      the kernel describe the GPL license text.  And there's unneeded stuff
      like the address (sometimes incorrect) for the FSF which is never
      needed.
      
      No copyright headers or other non-license-description text was removed.
      
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Halil Pasic <pasic@linux.vnet.ibm.com>
      Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      94bf2f28
    • Greg Kroah-Hartman's avatar
      s390: add SPDX identifiers to the remaining files · 0b73214f
      Greg Kroah-Hartman authored
      
      
      It's good to have SPDX identifiers in all files to make it easier to
      audit the kernel tree for correct licenses.
      
      Update the remaining arch/s390/ files with the correct SPDX license
      identifier based on the license text in the file itself.  The SPDX
      identifier is a legally binding shorthand, which can be used instead of
      the full boiler plate text.
      
      This work is based on a script and data from Thomas Gleixner, Philippe
      Ombredanne, and Kate Stewart.
      
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Kate Stewart <kstewart@linuxfoundation.org>
      Cc: Philippe Ombredanne <pombredanne@nexb.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Signed-off-by: default avatarMartin Schwidefsky <schwidefsky@de.ibm.com>
      0b73214f
  10. 09 Nov, 2017 1 commit
  11. 09 Oct, 2017 1 commit
  12. 29 Aug, 2017 1 commit
  13. 27 Jun, 2017 1 commit
    • QingFeng Hao's avatar
      KVM: s390: Backup the guest's machine check info · da72ca4d
      QingFeng Hao authored
      
      
      When a machine check happens in the guest, related mcck info (mcic,
      external damage code, ...) is stored in the vcpu's lowcore on the host.
      Then the machine check handler's low-level part is executed, followed
      by the high-level part.
      
      If the high-level part's execution is interrupted by a new machine check
      happening on the same vcpu on the host, the mcck info in the lowcore is
      overwritten with the new machine check's data.
      
      If the high-level part's execution is scheduled to a different cpu,
      the mcck info in the lowcore is uncertain.
      
      Therefore, for both cases, the further reinjection to the guest will use
      the wrong data.
      Let's backup the mcck info in the lowcore to the sie page
      for further reinjection, so that the right data will be used.
      
      Add new member into struct sie_page to store related machine check's
      info of mcic, failing storage address and external damage code.
      Signed-off-by: default avatarQingFeng Hao <haoqf@linux.vnet.ibm.com>
      Acked-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      da72ca4d
  14. 22 Jun, 2017 2 commits
  15. 04 Jun, 2017 1 commit
  16. 31 May, 2017 1 commit
  17. 21 Apr, 2017 1 commit
  18. 06 Apr, 2017 2 commits
  19. 22 Mar, 2017 1 commit
  20. 21 Mar, 2017 1 commit
  21. 16 Mar, 2017 1 commit
    • David Hildenbrand's avatar
      KVM: s390: use defines for execution controls · 0c9d8683
      David Hildenbrand authored
      
      
      Let's replace the bitmasks by defines. Reconstructed from code, comments
      and commit messages.
      
      Tried to keep the defines short and map them to feature names. In case
      they don't completely map to features, keep them in the stye of ICTL
      defines.
      
      This effectively drops all "U" from the existing numbers. I think this
      should be fine (as similarly done for e.g. ICTL defines).
      
      I am not 100% sure about the ECA_MVPGI and ECA_PROTEXCI bits as they are
      always used in pairs.
      Signed-off-by: default avatarDavid Hildenbrand <david@redhat.com>
      Message-Id: <20170313104828.13362-1-david@redhat.com>
      Signed-off-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      [some renames, add one missing place]
      0c9d8683
  22. 08 Sep, 2016 2 commits
    • David Hildenbrand's avatar
      KVM: s390: allow 255 VCPUs when sca entries aren't used · a6940674
      David Hildenbrand authored
      
      
      If the SCA entries aren't used by the hardware (no SIGPIF), we
      can simply not set the entries, stick to the basic sca and allow more
      than 64 VCPUs.
      
      To hinder any other facility from using these entries, let's properly
      provoke intercepts by not setting the MCN and keeping the entries
      unset.
      
      This effectively allows when running KVM under KVM (vSIE) or under z/VM to
      provide more than 64 VCPUs to a guest. Let's limit it to 255 for now, to
      not run into problems if the CPU numbers are limited somewhere else.
      Signed-off-by: default avatarDavid Hildenbrand <dahi@linux.vnet.ibm.com>
      Signed-off-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      a6940674
    • Suraj Jitindar Singh's avatar
      KVM: Add provisioning for ulong vm stats and u64 vcpu stats · 8a7e75d4
      Suraj Jitindar Singh authored
      
      
      vms and vcpus have statistics associated with them which can be viewed
      within the debugfs. Currently it is assumed within the vcpu_stat_get() and
      vm_stat_get() functions that all of these statistics are represented as
      u32s, however the next patch adds some u64 vcpu statistics.
      
      Change all vcpu statistics to u64 and modify vcpu_stat_get() accordingly.
      Since vcpu statistics are per vcpu, they will only be updated by a single
      vcpu at a time so this shouldn't present a problem on 32-bit machines
      which can't atomically increment 64-bit numbers. However vm statistics
      could potentially be updated by multiple vcpus from that vm at a time.
      To avoid the overhead of atomics make all vm statistics ulong such that
      they are 64-bit on 64-bit systems where they can be atomically incremented
      and are 32-bit on 32-bit systems which may not be able to atomically
      increment 64-bit numbers. Modify vm_stat_get() to expect ulongs.
      Signed-off-by: default avatarSuraj Jitindar Singh <sjitindarsingh@gmail.com>
      Reviewed-by: default avatarDavid Matlack <dmatlack@google.com>
      Acked-by: default avatarChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: default avatarPaul Mackerras <paulus@ozlabs.org>
      8a7e75d4
  23. 18 Jul, 2016 1 commit
  24. 21 Jun, 2016 3 commits
  25. 20 Jun, 2016 1 commit
  26. 10 Jun, 2016 4 commits