WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: mukesh.rathor@xxxxxxxxxx
Subject: [Xen-devel] Using kdb debugger on Xen-4.1
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
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to:cc :content-type; bh=RUQEJnhRo3GY+F8HFdXm4JzTWrXv7cgswxmDqcaZdvY=; b=RNVcpEw+CBHsrN0Ze/0Z1vDytH6+lqE2a88PKCe+M4UmyjCa0EiQpVzHzjPrh8SrFe EtCmtLSvm2eHfzBhzgBKZkkUhxniHcZDA7FI9UD0NZFLuWxfXtWePRe8TaFheMpizRuq KQU7hWBwxxbc90xuenwh9bcSVZGaXgc7ATk7s=
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=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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.

Attachment: get_processor_id.patch
Description: Text Data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>