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] credit scheduler and HYPERVISOR_yield()

To: John Levon <levon@xxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] credit scheduler and HYPERVISOR_yield()
From: Emmanuel Ackaouy <ackaouy@xxxxxxxxx>
Date: Tue, 9 Oct 2007 09:06:14 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 09 Oct 2007 00:06:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; bh=If66g/loKypRgTjMFA1/x2zS35dzrWJ5HKhOyKVJ8Ns=; b=lJFJ2RPslG6OH7nMf07lQwdxpV3mkkz0Y09kBNG+kMo7+2fIO0Baw8Q14HWH85OukfSH4Mj87+UkKHvAJPkxixcGBa9ix5d0t2HHAgR+oYkkQRxGpa1qNL+nX/L/46SU+ClofDBy1mZwx6sU76aqGXK/TfayYLCl+pxawrTfrIY=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:cc:from:subject:date:to:x-mailer; b=H7vwzRA4xH5w8JTFdam8l3hx0bLmlPm8zg73zbAy3E2aOQcRD4CGwIZapz+8YNItYuQkU22+Yu30/kGwO+LQqZjmsBSbb7GvNYDFT5Qef3n++6VtQOsbwj3vAdJxPRT5865WXYyWWW9ZYyVuUgQHdmNkEUYfe/lxR60aEgpgu1Y=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20071008234118.GA1396@xxxxxxxxxxxxxxxxxxxxxxx>
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: <20071008234118.GA1396@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi John.

The expected behavior of yield() (or any schedule operation really) is
that the current VCPU will be placed on the runq behind all VCPUs of
equal or greater priority.

Looking at __runq_insert() in sched_credit.c, it looks correct to me in
that respect.

Can you clarify what's going wrong?

On Oct 9, 2007, at 1:41, John Levon wrote:


It looks like a HYPERVISOR_yield() call will end placing the yielded
VCPU at the head of run queue if there are only equal-or-lower priority
VCPUs on the queue. Shouldn't it place it after any equal-priority CPUs
on the list?

thanks
john

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



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