[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] Using kdb debugger on Xen-4.1

  • To: mukesh.rathor@xxxxxxxxxx
  • From: Sergey Tovpeko <tsv.devel@xxxxxxxxx>
  • Date: Mon, 16 May 2011 18:01:12 +0400
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Mon, 16 May 2011 07:02:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=a3sG5IDeqXdD57DPfwj6WT/d1w4XaWkjxspesRJzHGeXbx51fSI3uUFt/Cay/ehB0s Hp7jWSAxxz4dKNjIM8r3psgiCbVNzgF/lrpmw/DcR7rvFvL+fysnyq+lQMJ4RmUN2GwU sX765fM0t52XdoWDeijc4c6vZf5CqzMZTVHtQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


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.


Attachment: get_processor_id.patch
Description: Text Data

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.