From: Keir Fraser <keir.xen@gmail.com>
To: Mukesh Rathor <mukesh.rathor@oracle.com>,
"Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>,
msw@amazon.com
Cc: Ben Guthro <ben@guthro.net>
Subject: Re: xen debugger (kdb/xdb/hdb) patch for c/s 25467
Date: Thu, 30 Aug 2012 00:18:18 +0100 [thread overview]
Message-ID: <CC6461CA.3D3AD%keir.xen@gmail.com> (raw)
In-Reply-To: <20120829143512.7c579fb1@mantra.us.oracle.com>
On 29/08/2012 22:35, "Mukesh Rathor" <mukesh.rathor@oracle.com> wrote:
> Hi Guys,
>
> Thanks for the interest in the xen hypervisor debugger, prev known as
> kdb. Btw. I'm gonna rename it to xdb for xen-debugger or hdb for
> hypervisor debugger. KDB is confusing people with linux kdb debugger
> and I often get emails where people think they need to apply linux kdb
> patch also...
>
> Anyways, attaching patch that is cleaned up of my debug code that I
> accidentally left in prev posting. Should apply cleanly to c/s 25467.
>
> JFYI... http://xenbits.xen.org/ext/debuggers.hg/ has gotten outdated,
> I wasn't sure if anyone was even looking at it. But, it looks like
> there is much interest, so I will just submit patch to Keir for
> his feedback on merging it in xen.
>
> Please voice your opinion here. Good seeing all at the summit :).
Split off the support bits you need scattered into Xen from the main bulk of
the debugger. Then we can review and apply those trickiest bits first.
-- Keir
> Thanks,
> Mukesh
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
prev parent reply other threads:[~2012-08-29 23:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 21:35 xen debugger (kdb/xdb/hdb) patch for c/s 25467 Mukesh Rathor
2012-08-29 21:41 ` Mukesh Rathor
2012-09-05 16:02 ` Ben Guthro
2012-09-05 18:52 ` Mukesh Rathor
2012-08-29 23:18 ` Keir Fraser [this message]
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=CC6461CA.3D3AD%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=Xen-devel@lists.xensource.com \
--cc=ben@guthro.net \
--cc=msw@amazon.com \
--cc=mukesh.rathor@oracle.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;
as well as URLs for NNTP newsgroup(s).