From: Ryan Harper <ryanh@us.ibm.com>
To: Stephan Diestelhorst <sd386@cl.cam.ac.uk>
Cc: Ryan Harper <ryanh@us.ibm.com>, xen-devel@lists.xensource.com
Subject: Re: scheduler independent forced vcpu selection
Date: Wed, 18 May 2005 09:55:44 -0500 [thread overview]
Message-ID: <20050518145544.GI7305@us.ibm.com> (raw)
In-Reply-To: <428B30BC.8070602@cl.cam.ac.uk>
* Stephan Diestelhorst <sd386@cl.cam.ac.uk> [2005-05-18 09:04]:
> Are you calling do_softirq directly? If not then it is quite strange,
No, I just call raise_softirq(SCHEDULE_SOFTIRQ); without a subsequent
do_softirq().
> that this assertion fails.
> The timer assertion might be the old scheduling timer, which gets
> probably reset, but not deleted beforehand... And the on runqueue
> assertion suggests that you are 'stealing' the domain from the
> schedulers queues without giving it a chance to notice.
Could you explain what 'giving it a chance to notice' means?
> I'd guess cloning do_block and appending code from __enter_scheduler
> with some checks (is the 'receiver' domain runnable? if not run proper
> sched.do_schedule) should give you a solid base to start from.
Let me add in a check for domain_runnable and see if that helps.
Thanks for the feedback. Let me know if you want me to post the patch
of where I'm at right now.
--
Ryan Harper
Software Engineer; Linux Technology Center
IBM Corp., Austin, Tx
(512) 838-9253 T/L: 678-9253
ryanh@us.ibm.com
next prev parent reply other threads:[~2005-05-18 14:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 20:48 scheduler independent forced vcpu selection Ryan Harper
2005-05-18 12:10 ` Stephan Diestelhorst
2005-05-18 14:55 ` Ryan Harper [this message]
2005-05-18 18:03 ` Ryan Harper
2005-05-19 13:22 ` Stephan Diestelhorst
2005-05-18 22:37 ` Ryan Harper
2005-05-19 13:25 ` Stephan Diestelhorst
2005-05-19 14:55 ` Ryan Harper
2005-05-19 15:05 ` Ryan Harper
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=20050518145544.GI7305@us.ibm.com \
--to=ryanh@us.ibm.com \
--cc=sd386@cl.cam.ac.uk \
--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.