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] Re: [RFC PATCH] Run the Mini-OS application in its own threa

To: "John D. Ramsdell" <ramsdell@xxxxxxxxx>
Subject: [Xen-devel] Re: [RFC PATCH] Run the Mini-OS application in its own thread.
From: "Jacob Gorm Hansen" <jacobg@xxxxxxx>
Date: Thu, 8 Jun 2006 14:03:22 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 08 Jun 2006 08:53:27 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=qm9DoCoYCfL7rWVWdAR9+/VEvUbkZCUJarAg0bwUwZGBuMPw1qMgEzi0TAeedE0iuAfgILedF24EkAgjtoSUhtozR2zn0/T6YzvlLfg7pkbY7IDUdln9JUh/FUoLFNOvc6iiPVV1p7hFugr8laa//iCiYu7Plw8ZDt9g35LPmLw=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <ogtd5djhp1h.fsf@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>
References: <E1FmGLS-000627-SM@host-192-168-0-1-bcn-london> <ogtd5djhp1h.fsf@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On 08 Jun 2006 07:20:26 -0400, John D. Ramsdell <ramsdell@xxxxxxxxx> wrote:
Some Xen developers have questioned why one would ever need to run a
Mini-OS application before thread scheduling is enabled.  I can see no
reason to do it.  If no one else can, I suggest each an application be
a thread function that is started in kernel.c.

I can, when writing a boot-loader there is no need for multiple
threads, so I would like the option of not having to start (and clean
up after) any.

Perhaps the last part of start_kernel() could be moved to a weak
function, that people like me can override?

Regards,
Jacob

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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