public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Gleb Natapov <gleb@redhat.com>
Subject: [PATCH 0/6] KVM: Enhancements and fixes around guest debugging
Date: Mon, 22 Feb 2010 18:51:17 +0100	[thread overview]
Message-ID: <cover.1266861080.git.jan.kiszka@siemens.com> (raw)

Patch 1&2 are well-known, but I think no longer disputed. Patch 3 was
requested by Avi while merging some qemu-kvm bits of mine, it should be
pushed into 2.6.33 as well. And the other patches came out of my attempt
to step over some APIC MMIO access of a guest.

So far my "stable" bits, the rest is currently waiting for feedback by
CPU vendors (NMI stepping on AMD, NMI injection vs. STI shadow on
Intel).

You may pull these patches from

	git://git.kiszka.org/linux-kvm gdb

Jan Kiszka (6):
  KVM: VMX: Update instruction length on intercepted BP
  KVM: SVM: Emulate nRIP feature when reinjecting INT3
  KVM: x86: Add KVM_CAP_X86_ROBUST_SINGLESTEP
  KVM: x86: Drop RF manipulation for guest single-stepping
  KVM: x86: Preserve injected TF across emulation
  KVM: x86: Emulator support for TF

 arch/x86/include/asm/kvm_host.h |    5 +++
 arch/x86/kvm/svm.c              |   72 +++++++++++++++++++++++++++----------
 arch/x86/kvm/vmx.c              |   19 ++++++++++
 arch/x86/kvm/x86.c              |   74 ++++++++++++++++++++++++++++++++------
 include/linux/kvm.h             |    1 +
 5 files changed, 139 insertions(+), 32 deletions(-)


             reply	other threads:[~2010-02-22 17:51 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 17:51 Jan Kiszka [this message]
2010-02-22 17:51 ` [PATCH 1/6] KVM: VMX: Update instruction length on intercepted BP Jan Kiszka
2010-02-22 17:51 ` [PATCH 2/6] KVM: SVM: Emulate nRIP feature when reinjecting INT3 Jan Kiszka
2010-02-23 10:13   ` Gleb Natapov
2010-02-23 10:17     ` Jan Kiszka
2010-02-23 10:23       ` Avi Kivity
2010-02-22 17:51 ` [PATCH 3/6] KVM: x86: Add KVM_CAP_X86_ROBUST_SINGLESTEP Jan Kiszka
2010-02-22 17:51 ` [PATCH 4/6] KVM: x86: Drop RF manipulation for guest single-stepping Jan Kiszka
2010-02-22 17:51 ` [PATCH 5/6] KVM: x86: Preserve injected TF across emulation Jan Kiszka
2010-02-23 10:00   ` Gleb Natapov
2010-02-23 10:13     ` Jan Kiszka
2010-02-23 10:31       ` Gleb Natapov
2010-02-23 10:40         ` Jan Kiszka
2010-02-23 11:03           ` Gleb Natapov
2010-02-22 17:51 ` [PATCH 6/6] KVM: x86: Emulator support for TF Jan Kiszka
2010-02-23  9:55   ` Gleb Natapov
2010-02-23 10:10     ` Jan Kiszka
2010-02-23 10:26       ` Gleb Natapov
2010-02-23 10:29         ` Avi Kivity
2010-02-23 10:32           ` Gleb Natapov
2010-02-23 10:34             ` Avi Kivity
2010-02-23 10:37         ` Jan Kiszka
2010-02-23 11:00           ` Gleb Natapov
2010-02-23 11:04             ` Avi Kivity
2010-02-23 11:30             ` Jan Kiszka
2010-02-23 11:41               ` Avi Kivity
2010-02-23 12:03                 ` Jan Kiszka
2010-02-23 12:05                 ` Gleb Natapov
2010-02-23 12:02               ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1266861080.git.jan.kiszka@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox