public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kvm-devel <kvm@vger.kernel.org>
Subject: Re: [RFT] Rebased gdb/debug register patches
Date: Tue, 25 Nov 2008 14:21:41 -0600	[thread overview]
Message-ID: <1227644501.7434.22.camel@localhost.localdomain> (raw)
In-Reply-To: <492AC7FA.6090100@siemens.com>

On Mon, 2008-11-24 at 16:27 +0100, Jan Kiszka wrote:
> Hi,
> 
> this is not yet the official submission, but a request for testing:
> 
> I'm happy to announce the availability of a rebased patch series to
> enhance KVM's guest debugging support as well as to add debug register
> emulation. It was rebased because QEMU mainline recently accepted the
> core of my corresponding bits and KVM has merged them over. A few
> patches are still awaiting QEMU merge, and two of them are mandatory to
> provide a clean foundation for the KVM changes - therefore this
> intermediate step.
> 
> To test the series, checkout the kernel bits from
> 
> 	git://git.kiszka.org/linux-kvm.git gdb-queue
> 
> and the user space part from
> 
> 	git://git.kiszka.org/kvm-userspace.git gdb-queue
> 
> Early feedback welcome, also before the final submission. And if someone
> could look into AMD/SVM implementation, this would also be great
> (unfortunately, there is no customer need for it ATM, thus no resources).

Would you mind posting the patches here, to make feedback easier for the
reviewers?

-- 
Hollis Blanchard
IBM Linux Technology Center


  reply	other threads:[~2008-11-25 20:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 15:27 [RFT] Rebased gdb/debug register patches Jan Kiszka
2008-11-25 20:21 ` Hollis Blanchard [this message]
2008-11-26  9:17   ` Jan Kiszka

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=1227644501.7434.22.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=jan.kiszka@siemens.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