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


[Xen-devel] [RFC] SMP & DEBUG config options

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC] SMP & DEBUG config options
From: Rik van Riel <riel@xxxxxxxxxx>
Date: Thu, 16 Feb 2006 10:57:56 -0500 (EST)
Delivery-date: Thu, 16 Feb 2006 16:10:21 +0000
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/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
Lately a lot of the Xen problems we have run into are related
to bugs that only trigger when using the DEBUG config options
and/or SMP.

I wonder if it would make sense to have those enabled in the
default install, so developers can notice bugs in their own
code before it gets committed and shipped off to dozens of
other developers elsewhere - who then have to spend days
trying to track down which changeset caused the problem...

Is there any good reason that the DEBUG config options and
SMP are not enabled in the default configuration?

All Rights Reversed

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>