public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: kvm-devel <kvm@vger.kernel.org>,
	Hollis Blanchard <hollisb@us.ibm.com>,
	Jerone Young <jyoung5@us.ibm.com>,
	Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH 0/11] Rework guest debug interface / x86 debug register support -v2
Date: Tue, 27 May 2008 12:50:20 +0300	[thread overview]
Message-ID: <483BD95C.1010309@qumranet.com> (raw)
In-Reply-To: <4839B14A.3010406@web.de>

Jan Kiszka wrote:
> Hi,
>
> here comes the full series of patches to fix and enhance debugging
> support of KVM. After completing hardware breakpoint support and
> reorganizing the patches, I felt like I should post them all in a single
> series, because my queue became quite long and potentially confusing in
> the meantime.
>
> The major changes or this revision are full hardware-assisted guest
> debugging and a lot of refactoring on the userspace side. The latter was
> motivated by an increasing inconsistency regarding which arch-specific
> part should be handled in libkvm and which by qemu. I decided to push
> everything into qemu, keeping the lib small (and easier to overcome one
> day :->).
>
> When I was trying to test the hardware breakpoint/watchpoint support
> with gdb, the first result with quite disappointing: current gdb is
> unable to handle such breakpoint remotely. There is hope, latest cvs has
> it fixed - but suffers from other regressions which make it unusable for
> kernel debugging. In the meantime, you can still write your own
> "maintenance packet Z2,..." requests. :p
>
> To give an overview of the series:
>  Patch 1..3  - Critical debugger fixes for KVM (should be merge in any
>                case)
>   

Applied 2, 3 (and my version of 1).

>  Patch 4..5  - QEMU refactoring, required for following KVM patches, but
>                also of generic use for QEMU (rebase and feature
>                enhancements are required to get them in shape for
>                upstream)
>   

These need to go into upstream first, otherwise we're just moving one 
patch queue into another.

>  Patch 6..8  - New guest debugging interface and SMP support
>  Patch 9..11 - Kernel-side changes for new guest debugging interface and
>                proper x86 debug register virtualization
>   

I'll do a proper review of these, but from a cursory look, all is well.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-05-27  9:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-26 22:05 [PATCH 0/11] Rework guest debug interface / x86 debug register support -v2 Jan Kiszka
2008-05-26 22:09 ` [PATCH 1/11] QEMU/KVM: Fix deadlocks in monitor and debugger Jan Kiszka
2008-05-27  9:36   ` Avi Kivity
2008-05-27 13:00     ` Jan Kiszka
2008-05-27 13:09       ` Avi Kivity
2008-05-26 22:09 ` [PATCH 2/11] QEMU/KVM: Cleanup and improve kvm_load/save_registers usage Jan Kiszka
2008-06-09 19:16   ` Anthony Liguori
2008-06-12 12:38     ` Avi Kivity
2008-05-26 22:09 ` [PATCH 3/11] QEMU/KVM: Proper vm_stop on debug events Jan Kiszka
2008-05-26 22:09 ` [PATCH 4/11] QEMU: Enhance cpu_break/watchpoint API and gdbstub integration Jan Kiszka
2008-05-26 22:10 ` [PATCH 5/11] QEMU: Improve SMP debugging support Jan Kiszka
2008-05-26 22:10 ` [PATCH 6/11] QEMU/KVM: Introduce single vcpu pause/resume Jan Kiszka
2008-05-26 22:10 ` [PATCH 7/11] QEMU/KVM: New guest debugging interface Jan Kiszka
2008-05-27 18:31   ` Jan Kiszka
2008-05-26 22:10 ` [PATCH 8/11] QEMU/KVM: Support for SMP guest debugging Jan Kiszka
2008-05-26 22:10 ` [PATCH 9/11] KVM: New guest debugging interface Jan Kiszka
2008-05-26 22:10 ` [PATCH 10/11] KVM-x86: Properly virtualize debug registers Jan Kiszka
2008-05-26 22:10 ` [PATCH 11/11] KVM-x86: Wire up host-managed " Jan Kiszka
2008-05-27  9:50 ` Avi Kivity [this message]
2008-05-27 10:44   ` [PATCH 0/11] Rework guest debug interface / x86 debug register support -v2 Jan Kiszka
2008-05-27 18:46   ` Hollis Blanchard

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=483BD95C.1010309@qumranet.com \
    --to=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=jan.kiszka@web.de \
    --cc=joerg.roedel@amd.com \
    --cc=jyoung5@us.ibm.com \
    --cc=kvm@vger.kernel.org \
    /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