Re: [patch] BFS 420: remove for_each_flag_domain

From: Hillf Danton
Date: Thu May 24 2012 - 07:44:11 EST


On Wed, May 23, 2012 at 8:56 PM, Hillf Danton <dhillf@xxxxxxxxx> wrote:
> The macro, for_each_flag_domain, is no longer used, so remove.
>
> --- a/kernel/sched/bfs.c    ÂMon May 14 20:50:38 2012
> +++ b/kernel/sched/bfs.c    ÂWed May 23 20:09:32 2012
> @@ -4951,42 +4951,6 @@ void select_nohz_load_balancer(int stop_
> Â}
>
> Âvoid set_cpu_sd_state_idle(void) {}
> -#if defined(CONFIG_SCHED_MC) || defined(CONFIG_SCHED_SMT)
> -/**
> - * lowest_flag_domain - Return lowest sched_domain containing flag.
> - * @cpu: Â Â Â The cpu whose lowest level of sched domain is to
> - * Â Â Â Â Â Â be returned.
> - * @flag: Â Â ÂThe flag to check for the lowest sched_domain
> - * Â Â Â Â Â Â for the given cpu.
> - *
> - * Returns the lowest sched_domain of a cpu which contains the given flag.
> - */
> -static inline struct sched_domain *lowest_flag_domain(int cpu, int flag)
> -{
> - Â Â Â struct sched_domain *sd;
> -
> - Â Â Â for_each_domain(cpu, sd)
> - Â Â Â Â Â Â Â if (sd && (sd->flags & flag))
> - Â Â Â Â Â Â Â Â Â Â Â break;
> -
> - Â Â Â return sd;
> -}
> -
> -/**
> - * for_each_flag_domain - Iterates over sched_domains containing the flag.
> - * @cpu: Â Â Â The cpu whose domains we're iterating over.
> - * @sd: Â Â Â Â Â Â Â Âvariable holding the value of the power_savings_sd
> - * Â Â Â Â Â Â for cpu.
> - * @flag: Â Â ÂThe flag to filter the sched_domains to be iterated.
> - *
> - * Iterates over all the scheduler domains for a given cpu that has the 'flag'
> - * set, starting from the lowest sched_domain to the highest.
> - */
> -#define for_each_flag_domain(cpu, sd, flag) \
> - Â Â Â for (sd = lowest_flag_domain(cpu, flag); \
> - Â Â Â Â Â Â Â (sd && (sd->flags & flag)); sd = sd->parent)
> -
> -#endif /* Â(CONFIG_SCHED_MC || CONFIG_SCHED_SMT) */
>
> Âstatic inline void resched_cpu(int cpu)
> Â{
> --
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/