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/
Home Products Support Community News


Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c

To: Ed Smith <esmith@xxxxxxxxxxxxxxx>, Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 11616
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 26 Sep 2006 17:28:32 +0100
Cc: Xen Devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 26 Sep 2006 09:27:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <45194844.2080806@xxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcbhiM5TDLinpk18EduAkQAX8io7RQ==
Thread-topic: [Xen-devel] Testing status of HVM (Intel VT) on 64bit XEN unstable c/s 11616
User-agent: Microsoft-Entourage/
On 26/9/06 16:33, "Ed Smith" <esmith@xxxxxxxxxxxxxxx> wrote:

>> any chance you can test with debug=y ? The back-traces aren't
>> really very useful otherwise.
> These are automated builds and tests that run each night.  We don't
> normally build a debug XEN as we try and test the bits a customer
> would run.  If these backtraces are useful in the release build how
> will we diagnose crashes on a customer's site?

They take more deciphering, sometimes with the aid of the xen-syms file, as
the backtrace contains functions that aren't really in the call chain (and
misses some that are). It's less time consuming with a debug build, and
there's less reliance on the xen-syms file, as we include frame pointers.

Trying to match customer bits doesn't make sense. There is no customer for
these bits! So why throw away debug info during development testing just
because there are situations where debug info is not available? Is it
considered good training for developers? :-)

 -- Keir

Xen-devel mailing list