1. 18 2月, 2015 1 次提交
  2. 12 1月, 2015 1 次提交
  3. 23 9月, 2014 2 次提交
  4. 08 7月, 2014 1 次提交
  5. 10 6月, 2014 3 次提交
  6. 20 5月, 2014 1 次提交
  7. 07 5月, 2014 1 次提交
    • C
      s390x/css: Don't save orb in subchannel. · 56bf1a8e
      Cornelia Huck 提交于
      Current css code saves the operation request block (orb) in the
      subchannel structure for later consumption by the start function
      handler. This might make sense for asynchronous execution of the
      start function (which qemu doesn't support), but not in our case;
      it would even be wrong since orb contains a reference to a local
      variable in the base ssch handler.
      
      Let's just pass the orb through the start function call chain for
      ssch; for rsch, we can pass NULL as the backend function does not
      use any information passed via the orb there.
      Acked-by: NChristian Borntraeger <borntraeger@de.ibm.com>
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      56bf1a8e
  8. 05 3月, 2014 1 次提交
  9. 11 2月, 2014 4 次提交
  10. 01 9月, 2013 1 次提交
  11. 25 6月, 2013 1 次提交
  12. 06 6月, 2013 1 次提交
  13. 09 3月, 2013 1 次提交
  14. 14 2月, 2013 1 次提交
    • C
      s390: Fix handling of iscs. · 91b0a8f3
      Cornelia Huck 提交于
      There are two ways to express an interruption subclass:
      - As a bitmask, as used in cr6.
      - As a number, as used in the I/O interruption word.
      
      Unfortunately, we have treated to I/O interruption word as if it
      contained the bitmask as well, which went unnoticed so far as
      - (queued-for-next) kvm made the same mistake, and
      - Linux guest kernels don't check the isc value in the I/O interruption
        word for subchannel interrupts.
      
      Make sure that we treat the I/O interruption word correctly.
      Signed-off-by: NCornelia Huck <cornelia.huck@de.ibm.com>
      Signed-off-by: NAlexander Graf <agraf@suse.de>
      91b0a8f3
  15. 30 1月, 2013 3 次提交