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 still broken?

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Diwaker Gupta <diwakergupta@xxxxxxxxx>
Subject: Re: [Xen-devel] atropos still broken?
From: Mark Williamson <Mark.Williamson@xxxxxxxxxxxx>
Date: Fri, 28 Jan 2005 02:43:17 +0000
Delivery-date: Fri, 28 Jan 2005 06:01:41 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <1b0b4557050126202540ed6469@xxxxxxxxxxxxxx>
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: <1b0b4557050126202540ed6469@xxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.7.1
> This is for Xen 2.0.3. I'm really interested in the functionality of
> atropos (enforcing CPU partitioning in a non work-conserving fashion).
> As I had reported earlier, atropos seemed broken in 2.0. It still
> seems broken now:

Yes - it's still broken because I still haven't fixed it :-(

> So it seems atropos is still broken. Is a fix being worked upon? I'd

Fixing Atropos is still on my todo list.  One of the other developers is 
working on an alternative deadline-based scheduler, which may behave better.

> scheduling code; if any of the developers have any idea of where/what
> the bug is, I'd like to take a crack at it.

I don't know where the bug is - it appears to be something quite subtle since 
the code *looks* OK to the people who have read through it...  Analysing some 
trace buffer output might help us figure out what it's actually doing and 
why.

I'd still like to look at this myself but you're welcome to take a shot at 
debugging it if you're feeling enthusiastic!

Cheers,
Mark


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel

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