From: Emmanuel Ackaouy <ackaouy@gmail.com>
To: John Levon <levon@movementarian.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: credit scheduler and HYPERVISOR_yield()
Date: Tue, 9 Oct 2007 09:06:14 +0200 [thread overview]
Message-ID: <7e903d73fbea1bb8ca97396fef058b2b@gmail.com> (raw)
In-Reply-To: <20071008234118.GA1396@totally.trollied.org.uk>
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@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
next prev parent reply other threads:[~2007-10-09 7:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-08 23:41 credit scheduler and HYPERVISOR_yield() John Levon
2007-10-09 1:23 ` Atsushi SAKAI
2007-10-09 1:42 ` John Levon
2007-10-09 7:06 ` Emmanuel Ackaouy [this message]
2007-10-09 12:15 ` John Levon
2007-10-09 13:22 ` George Dunlap
2007-10-09 14:48 ` Emmanuel Ackaouy
2007-10-14 18:45 ` John Levon
2007-10-14 19:20 ` Emmanuel Ackaouy
2007-10-14 19:49 ` John Levon
2007-10-14 21:25 ` Emmanuel Ackaouy
2007-10-14 21:50 ` John Levon
2007-10-15 12:26 ` George Dunlap
2007-10-15 12:32 ` John Levon
2007-10-15 12:43 ` Samuel Thibault
2007-10-15 17:13 ` Emmanuel Ackaouy
2007-10-15 17:45 ` Keir Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7e903d73fbea1bb8ca97396fef058b2b@gmail.com \
--to=ackaouy@gmail.com \
--cc=levon@movementarian.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.