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-ia64-devel] RE: [Xen-devel] RE: [Patch] Fix IDLE issue with sedf sc

To: "Magenheimer, Dan \(HP Labs Fort Collins\)" <dan.magenheimer@xxxxxx>
Subject: [Xen-ia64-devel] RE: [Xen-devel] RE: [Patch] Fix IDLE issue with sedf scheduler on IA64
From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
Date: Fri, 15 Jul 2005 11:18:08 +0800
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 15 Jul 2005 03:16:47 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: DIscussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcWHkNam4njROoPTSRq2Lw7NMoU4SwAE6cuAAAJhJYAAA5hiwAAW6AAgABzA0JAAF7VhMA==
Thread-topic: [Xen-devel] RE: [Patch] Fix IDLE issue with sedf scheduler on IA64
>From: Magenheimer, Dan (HP Labs Fort Collins)
>Sent: Thursday, July 14, 2005 11:52 PM
>> >I think domain0 only goes in the waitq at one point -- when
>> >it calls pal_halt_light to idle its virtual machine.  This
>> >case could be easily changed (there is already some code there)
>> >to ensure domain0 is always runnable.
>> As I said in another mail, too many pal_halt_light in Dom0's
>> idle loop is even worse than current IDLE domain. (At lease
>> unmodified dom0 can't change that behavior)
>You misunderstand what I was suggesting:  When the hypervisor
>recognizes that a domain did a pal_halt_light:
>if (current == dom0) {
>       if (current is_the_only_non_idle_domain_on_the_run_queue) {
>               REAL_pal_halt_light;  // processor to low power state
>               return; // back to domain0
>      }
>      else do_sched_op(SCHEDOP_yield);
>else do_sched_op(SCHEDOP_yield);

Sounds good, and then you need help from scheduler to export that
important runqueue information. Also, for (current != dom0),
SCHEDOP_block is better than SCHEDOP_yield to emulate pal_halt_light...


Xen-ia64-devel mailing list

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