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

Re: [Xen-devel] atropos scheduler params

To: mark.williamson@xxxxxxxxxxxx
Subject: Re: [Xen-devel] atropos scheduler params
From: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Date: Sat, 16 Oct 2004 19:03:18 -0700
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 17 Oct 2004 03:27:03 +0100
Domainkey-signature: a=rsa-sha1; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=YNZH5j+DuNp1L/ODqYaHfp7pjcszH7oi4KuZ7AOz1ZOclsbWlSlS15RakNoHe1D3xU8tpTTd1Ybixm29ZPkYqEzSp4Qz7kKVLqKiFxZsbpQhMg2xpTbStHt6LuyjCRnKsSMFZO5lb3DtRouZjw99mlmbKCrZ4EK7ASph0Bzk7o4
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: <200410150020.00911.mark.williamson@xxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <1b0b4557041014154678dd30@xxxxxxxxxxxxxx> <200410150020.00911.mark.williamson@xxxxxxxxxxxx>
Reply-to: Diwaker Gupta <diwakergupta@xxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > But the machine failts to boot with a "CPU 0 is toasted" type of
> > message! :-O If remove the sched param, things work just fine again.
> > Any ideas?
> 
> That looks right.  The Atropos port is probably broken at the moment as it's
> in the process of being updated to the latest scheduler interface.

So this is 2.0 unstable specific, or applies to 1.2 as well? Also, is
someone working on this (I haven't checked the latest nightly, so
apologize if I'm not up-todate) already, otherwise I might want to
look into it.

Thx,
-- 
Diwaker Gupta
http://resolute.ucsd.edu/diwaker


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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