Re: [Xen-devel] xen cpu scheduler internals

2016-04-18 Thread tutu sky
ay, April 18, 2016 9:07 AM To: tutu sky Cc: Xen-devel@lists.xen.org Subject: Re: [Xen-devel] xen cpu scheduler internals On Sun, Apr 17, 2016 at 7:18 PM, tutu sky wrote: > Hi, > I know that scheduling is done via two main functions and their effective > interaction: > one '

Re: [Xen-devel] xen cpu scheduler internals

2016-04-18 Thread George Dunlap
On Sun, Apr 17, 2016 at 7:18 PM, tutu sky wrote: > Hi, > I know that scheduling is done via two main functions and their effective > interaction: > one 'schedule()' in schedule.c and another 'do_schedule(...)', which is > specific for every scheduling policy. > my question is that (although it m

Re: [Xen-devel] xen cpu scheduler internals

2016-04-18 Thread tutu sky
Hi, I think pick_cpu function in schedule.c can be a good starting point, am i right? From: tutu sky Sent: Sunday, April 17, 2016 6:18 PM To: Xen-devel@lists.xen.org Subject: xen cpu scheduler internals Hi, I know that scheduling is done via two main fun

[Xen-devel] xen cpu scheduler internals

2016-04-17 Thread tutu sky
Hi, I know that scheduling is done via two main functions and their effective interaction: one 'schedule()' in schedule.c and another 'do_schedule(...)', which is specific for every scheduling policy. my question is that (although it may seem clear and very common for kernel developers, but not