From: Mukesh Rathor <mukesh.rathor@oracle.com>
To: Sergey Tovpeko <tsv.devel@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Using kdb debugger on Xen-4.1
Date: Tue, 17 May 2011 19:11:26 -0700 [thread overview]
Message-ID: <20110517191126.37fbcedc@mantra.us.oracle.com> (raw)
In-Reply-To: <BANLkTikzBoOCHQtA2hMpPvMU9rWsXVAR1g@mail.gmail.com>
Hi Sergey,
Yeah, I noticed that on my prev refresh a while ago, and its sitting
in my list of things to do. I hope to return to it soon and refresh my
kdb branch on xen.org.
thanks,
Mukesh
On Mon, 16 May 2011 18:01:12 +0400
Sergey Tovpeko <tsv.devel@gmail.com> wrote:
> Hello!
>
> I've tried kdb on Xen 4.1 to debug hypervisor&Dom0 online and I should
> say it works well.
> Took kdb from http://xenbits.xen.org/ext/debuggers.hg/
>
> It seems there are still one issue I run into.
>
> GET_PROCESSOR_ID macros defined in arch/x86/x86_64/entry.S is
> out-of-date and should be updated for Xen-4.1. I mean that one uses
> fixed offset to get processor_id field.
>
> orq $(STACK_SIZE-16),reg; \
>
>
> That offset has been changed in cpu_info structure in new Xen.
>
> I attached the patch how it should be fixed on my vision. Please,
> review the one.
>
> Sergey.
prev parent reply other threads:[~2011-05-18 2:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 14:01 Using kdb debugger on Xen-4.1 Sergey Tovpeko
2011-05-18 2:11 ` Mukesh Rathor [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=20110517191126.37fbcedc@mantra.us.oracle.com \
--to=mukesh.rathor@oracle.com \
--cc=tsv.devel@gmail.com \
--cc=xen-devel@lists.xensource.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).