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

Re: [Xen-devel] Scheduler portability problem




On 8 Mar 2005, at 22:46, Magenheimer, Dan (HP Labs Fort Collins) wrote:

Bottom line: The current code in __enter_scheduler() does not easily
accommodate other architectures.  I'll be taking a look at what it
will take to "fix" it, but wanted to open discussion first.  I know
there are some that will say "just change the ia64 code"... because
of architectural constraints, this is far FAR more easily said than
done.  And there are some that will say that mimicking Linux is
a mistake because XINL (Xen is not Linux).  However, I believe this
is a case where leveraging the many many years of experience on many
many architectures (with said experience only documented in the code
itself) of Linux will benefit Xen portability in the long run (and,
in my case, in the short run).

I've changed the tail of __enter_scheduler() to call a new arch-specific function context_switch(). This subsumes switch_to() and schedule_tail() so should give you the freedom to do what you require.

 -- Keir



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel


 


Rackspace

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