|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v2] sched: print information about scheduling granularity
On 20.04.20 15:06, Sergey Dyasli wrote: This is misleading. You are using the per-cpupool values, but they are all the same right now. Signed-off-by: Sergey Dyasli <sergey.dyasli@xxxxxxxxxx> --- v2: - print information on a separate line - use per-cpupool granularity - updated commit message CC: Juergen Gross <jgross@xxxxxxxx> CC: Dario Faggioli <dfaggioli@xxxxxxxx> CC: George Dunlap <george.dunlap@xxxxxxxxxx> CC: Jan Beulich <jbeulich@xxxxxxxx> --- xen/common/sched/cpupool.c | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/xen/common/sched/cpupool.c b/xen/common/sched/cpupool.c index d40345b585..68106f6c15 100644 --- a/xen/common/sched/cpupool.c +++ b/xen/common/sched/cpupool.c @@ -40,6 +40,30 @@ static DEFINE_SPINLOCK(cpupool_lock); static enum sched_gran __read_mostly opt_sched_granularity = SCHED_GRAN_cpu; static unsigned int __read_mostly sched_granularity = 1;+static void sched_gran_print(enum sched_gran mode, unsigned int gran) With this addition it might make sense to have an array indexed by mode to get the string. This array could then be used in sched_select_granularity(), too.
Juergen
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |