[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] credit scheduler and HYPERVISOR_yield()


  • To: John Levon <levon@xxxxxxxxxxxxxxxxx>
  • 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
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.