1. 06 12月, 2017 2 次提交
    • G
      KVM: s390: Remove redundant license text · 940f89a5
      Greg Kroah-Hartman 提交于
      Now that the SPDX tag is in all arch/s390/kvm/ 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: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Message-Id: <20171124140043.10062-9-gregkh@linuxfoundation.org>
      Acked-by: NCornelia Huck <cohuck@redhat.com>
      Acked-by: N"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      940f89a5
    • G
      KVM: s390: add SPDX identifiers to the remaining files · d809aa23
      Greg Kroah-Hartman 提交于
      It's good to have SPDX identifiers in all files to make it easier to
      audit the kernel tree for correct licenses.
      
      Update the arch/s390/kvm/ 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: Christian Borntraeger <borntraeger@de.ibm.com>
      Cc: Cornelia Huck <cohuck@redhat.com>
      Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
      Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
      Cc: Thomas Gleixner <tglx@linutronix.de>
      Cc: Kate Stewart <kstewart@linuxfoundation.org>
      Cc: Philippe Ombredanne <pombredanne@nexb.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      Message-Id: <20171124140043.10062-3-gregkh@linuxfoundation.org>
      Acked-by: NCornelia Huck <cohuck@redhat.com>
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      d809aa23
  2. 28 8月, 2017 1 次提交
  3. 21 6月, 2016 1 次提交
  4. 09 5月, 2016 1 次提交
  5. 19 11月, 2015 1 次提交
  6. 29 7月, 2015 2 次提交
  7. 17 3月, 2015 1 次提交
  8. 06 3月, 2015 1 次提交
  9. 23 1月, 2015 4 次提交
  10. 28 11月, 2014 1 次提交
  11. 28 10月, 2014 6 次提交
  12. 30 7月, 2014 1 次提交
  13. 21 7月, 2014 2 次提交
  14. 10 7月, 2014 1 次提交
  15. 30 5月, 2014 1 次提交
  16. 16 5月, 2014 1 次提交
    • D
      KVM: s390: interpretive execution of SIGP EXTERNAL CALL · 4953919f
      David Hildenbrand 提交于
      If the sigp interpretation facility is installed, most SIGP EXTERNAL CALL
      operations will be interpreted instead of intercepted. A partial execution
      interception will occurr at the sending cpu only if the target cpu is in the
      wait state ("W" bit in the cpuflags set). Instruction interception will only
      happen in error cases (e.g. cpu addr invalid).
      
      As a sending cpu might set the external call interrupt pending flags at the
      target cpu at every point in time, we can't handle this kind of interrupt using
      our kvm interrupt injection mechanism. The injection will be done automatically
      by the SIE when preparing the start of the target cpu.
      Signed-off-by: NDavid Hildenbrand <dahi@linux.vnet.ibm.com>
      Reviewed-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      CC: Thomas Huth <thuth@linux.vnet.ibm.com>
      [Adopt external call injection to check for sigp interpretion]
      Signed-off-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      4953919f
  17. 22 4月, 2014 1 次提交
  18. 25 3月, 2014 1 次提交
  19. 04 3月, 2014 2 次提交
  20. 30 1月, 2014 1 次提交
  21. 12 12月, 2013 4 次提交
  22. 28 11月, 2013 3 次提交
  23. 21 6月, 2013 1 次提交