1. 20 Oct, 2014 1 commit
  2. 25 Sep, 2014 1 commit
  3. 22 Sep, 2014 2 commits
  4. 22 Aug, 2014 1 commit
  5. 20 Aug, 2014 1 commit
  6. 15 Aug, 2014 1 commit
  7. 04 Jun, 2014 1 commit
    • Stefan Hajnoczi's avatar
      blkdebug: use BlockDriverState's AioContext · 7e1efdf0
      Stefan Hajnoczi authored
      Drop the assumption that we're using the main AioContext.  Convert
      qemu_bh_new() to aio_bh_new() so we use the BlockDriverState's
      AioContext.
      
      The .bdrv_detach_aio_context() and .bdrv_attach_aio_context() interfaces
      are not needed since no fd handlers, timers, or BHs stay registered when
      requests have been drained.
      
      Cc: Kevin Wolf <kwolf@redhat.com>
      Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
      7e1efdf0
  8. 21 Feb, 2014 2 commits
  9. 17 Feb, 2014 1 commit
  10. 09 Feb, 2014 1 commit
  11. 24 Jan, 2014 2 commits
  12. 22 Jan, 2014 6 commits
  13. 06 Jan, 2014 1 commit
  14. 13 Dec, 2013 1 commit
  15. 29 Nov, 2013 1 commit
  16. 11 Oct, 2013 1 commit
  17. 12 Sep, 2013 2 commits
  18. 02 Sep, 2013 1 commit
  19. 06 Jun, 2013 1 commit
  20. 22 Apr, 2013 2 commits
  21. 22 Mar, 2013 1 commit
  22. 19 Dec, 2012 3 commits
  23. 12 Dec, 2012 3 commits
    • Kevin Wolf's avatar
      blkdebug: Implement suspend/resume of AIO requests · 3c90c65d
      Kevin Wolf authored
      This allows more systematic AIO testing. The patch adds three new
      operations to blkdebug:
      
       * Setting a "breakpoint" on a blkdebug event. The next request that
         triggers this breakpoint is suspended and is tagged with a name.
         The breakpoint is removed after a request has triggered it.
      
       * A suspended request (identified by it's tag) can be resumed
      
       * It's possible to check whether a suspended request with a given
         tag exists. This can be used for waiting for an event.
      
      Ideally, we would instead tag requests right when they are created and
      set breakpoints for individual requests. However, at this point the
      block layer doesn't allow this easily, and breakpoints that trigger for
      any request already allow a lot of useful testing.
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      3c90c65d
    • Kevin Wolf's avatar
      blkdebug: Factor out remove_rule() · 9e35542b
      Kevin Wolf authored
      The cleanup work to remove a rule depends on the type of the rule. It's
      easy for the existing rules as there is no data that must be cleaned up
      and is specific to a type yet, but the next patch will change this.
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      9e35542b
    • Kevin Wolf's avatar
      blkdebug: Allow usage without config file · 312a2ba0
      Kevin Wolf authored
      As soon as new rules can be set during runtime, as introduced by the
      next patch, blkdebug makes sense even without a config file.
      Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
      312a2ba0
  24. 14 Nov, 2012 1 commit
  25. 28 Sep, 2012 1 commit
  26. 09 Jul, 2012 1 commit