Re: [tip: sched/core] sched/topology: Introduce sched_group::flags
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip: sched/core] sched/topology: Introduce sched_group::flags
- From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
- Date: Tue, 23 May 2023 12:59:35 +0200
- Cc: linux-tip-commits@xxxxxxxxxxxxxxx, Ricardo Neri <ricardo.neri-calderon@xxxxxxxxxxxxxxx>, "Joel Fernandes (Google)" <joel@xxxxxxxxxxxxxxxxx>, Len Brown <len.brown@xxxxxxxxx>, Vincent Guittot <vincent.guittot@xxxxxxxxxx>, x86@xxxxxxxxxx
- In-reply-to: <163344312261.25758.16010066552550079330.tip-bot2@tip-bot2>
- References: <20210911011819.12184-3-ricardo.neri-calderon@linux.intel.com> <163344312261.25758.16010066552550079330.tip-bot2@tip-bot2>
On Tue, Oct 05, 2021 at 02:12:02PM -0000, tip-bot2 for Ricardo Neri wrote:
> index 4e8698e..c56faae 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -716,8 +716,20 @@ cpu_attach_domain(struct sched_domain *sd, struct root_domain *rd, int cpu)
> tmp = sd;
> sd = sd->parent;
> destroy_sched_domain(tmp);
> - if (sd)
> + if (sd) {
> + struct sched_group *sg = sd->groups;
> +
> + /*
> + * sched groups hold the flags of the child sched
> + * domain for convenience. Clear such flags since
> + * the child is being destroyed.
> + */
> + do {
> + sg->flags = 0;
> + } while (sg != sd->groups);
I happened to be reading this here code and aren't we missing:
sg = sg->next;
somewhere in that loop?
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]