1. 14 Apr, 2009 1 commit
  2. 03 Apr, 2009 1 commit
  3. 31 Mar, 2009 1 commit
  4. 26 Mar, 2009 18 commits
  5. 24 Mar, 2009 2 commits
    • Jan Kiszka's avatar
      KVM: Remove old kvm_guest_debug structs · 989c0f0e
      Jan Kiszka authored
      Remove the remaining arch fragments of the old guest debug interface
      that now break non-x86 builds.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
    • Jan Kiszka's avatar
      KVM: New guest debug interface · d0bfb940
      Jan Kiszka authored
      This rips out the support for KVM_DEBUG_GUEST and introduces a new IOCTL
      instead: KVM_SET_GUEST_DEBUG. The IOCTL payload consists of a generic
      part, controlling the "main switch" and the single-step feature. The
      arch specific part adds an x86 interface for intercepting both types of
      debug exceptions separately and re-injecting them when the host was not
      interested. Moveover, the foundation for guest debugging via debug
      registers is layed.
      To signal breakpoint events properly back to userland, an arch-specific
      data block is now returned along KVM_EXIT_DEBUG. For x86, the arch block
      contains the PC, the debug exception, and relevant debug registers to
      tell debug events properly apart.
      The availability of this new interface is signaled by
      KVM_CAP_SET_GUEST_DEBUG. Empty stubs for not yet supported archs are
      Note that both SVM and VTX are supported, but only the latter was tested
      yet. Based on the experience with all those VTX corner case, I would be
      fairly surprised if SVM will work out of the box.
      Signed-off-by: Jan Kiszka's avatarJan Kiszka <jan.kiszka@siemens.com>
      Signed-off-by: default avatarAvi Kivity <avi@redhat.com>
  6. 20 Mar, 2009 1 commit
  7. 18 Mar, 2009 3 commits
  8. 19 Feb, 2009 2 commits
  9. 16 Feb, 2009 1 commit
    • Patrick Ohly's avatar
      net: new user space API for time stamping of incoming and outgoing packets · cb9eff09
      Patrick Ohly authored
      User space can request hardware and/or software time stamping.
      Reporting of the result(s) via a new control message is enabled
      separately for each field in the message because some of the
      fields may require additional computation and thus cause overhead.
      User space can tell the different kinds of time stamps apart
      and choose what suits its needs.
      When a TX timestamp operation is requested, the TX skb will be cloned
      and the clone will be time stamped (in hardware or software) and added
      to the socket error queue of the skb, if the skb has a socket
      associated with it.
      The actual TX timestamp will reach userspace as a RX timestamp on the
      cloned packet. If timestamping is requested and no timestamping is
      done in the device driver (potentially this may use hardware
      timestamping), it will be done in software after the device's
      start_hard_xmit routine.
      Signed-off-by: default avatarPatrick Ohly <patrick.ohly@intel.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
  10. 11 Feb, 2009 1 commit
  11. 23 Jan, 2009 1 commit
  12. 15 Jan, 2009 1 commit
  13. 09 Jan, 2009 5 commits
  14. 07 Jan, 2009 1 commit
  15. 06 Jan, 2009 1 commit