1. 26 Dec, 2014 4 commits
    • Pavel Emelyanov's avatar
      95945950
    • Pavel Emelyanov's avatar
      aio: Restore AIO contexts · 2694a74a
      Pavel Emelyanov authored
      Restoring AIO is quite simple. Once all VMAs are put in
      their places we can call io_setup() to let kernel create
      the context back and then move the ring into proper place.
      
      Another thing we should "restore" is the context ID. But
      the thing is, upon ring creation kernel repots the ring
      start address as this ID. And there's a patch in the -next
      tree that changes the ID when we remap the ring. That
      said after AIO context creation and ring remap we need
      to check that the new ID is seen by the kernel.
      Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
      2694a74a
    • Pavel Emelyanov's avatar
      aio: Dump AIO rings · 08c20482
      Pavel Emelyanov authored
      When AIO context is set up kernel does two things:
      
      1. creates an in-kernel aioctx object
      2. maps a ring into process memory
      
      The 2nd thing gives us all the needed information
      about how the AIO was set up. So, in order to dump
      one we need to pick the ring in memory and get all
      the information we need from it.
      
      One thing to note -- we cannot dump tasks if there
      are any AIO requests pending. So we also need to
      go to parasite and check the ring to be empty.
      Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
      08c20482
    • Pavel Emelyanov's avatar
      x86: Add io syscalls · 80cf0426
      Pavel Emelyanov authored
      Signed-off-by: 's avatarPavel Emelyanov <xemul@parallels.com>
      80cf0426
  2. 25 Dec, 2014 4 commits
  3. 24 Dec, 2014 2 commits
  4. 22 Dec, 2014 13 commits
  5. 19 Dec, 2014 10 commits
  6. 17 Dec, 2014 3 commits
  7. 11 Dec, 2014 1 commit
  8. 10 Dec, 2014 3 commits