mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Xuewen Yan <xuewen.yan94@gmail.com>
Cc: Lukasz Luba <lukasz.luba@arm.com>,
	Xuewen Yan <xuewen.yan@unisoc.com>,
	rafael@kernel.org, mingo@redhat.com, peterz@infradead.org,
	juri.lelli@redhat.com, vincent.guittot@linaro.org,
	dietmar.eggemann@arm.com, rostedt@goodmis.org,
	bsegall@google.com, mgorman@suse.de, bristot@redhat.com,
	linux-kernel@vger.kernel.org, ke.wang@unisoc.com,
	xuewyan@foxmail.com, linux-pm@vger.kernel.org
Subject: Re: [PATCH] sched/schedutil: Fix deadlock between cpuset and cpu hotplug when using schedutil
Date: Mon, 11 Jul 2022 13:17:24 +0530	[thread overview]
Message-ID: <20220711074724.tbwefl42fpf2aq5a@vireshk-i7> (raw)
In-Reply-To: <CAB8ipk_Y5vaUMnRQVJsbHUue_J00qqy0E1ifu3W_hFSspL1r1w@mail.gmail.com>

On 11-07-22, 15:43, Xuewen Yan wrote:
> This deadlock occurs when we run the monkey test on an Android phone,
> at the same time, randomly put online or offline a cpu core.
> Indeed the thread-A which get the cgroup_threadgroup_rwsem and waiting
> for the cpu_hotplug_lock is the thread whose name is "OomAdjuster" in
> android.

It would be better to reproduce this on mainline kernel, no android,
and tell us the steps. We don't want to chase an Android only issue,
just in case.

Thanks.

-- 
viresh

  reply	other threads:[~2022-07-11  7:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-05 12:37 Xuewen Yan
2022-07-11  7:21 ` Xuewen Yan
2022-07-11  7:32   ` Lukasz Luba
2022-07-11  7:43     ` Xuewen Yan
2022-07-11  7:47       ` Viresh Kumar [this message]
2022-07-11  7:50       ` Lukasz Luba
2022-07-11 17:46 ` Qais Yousef
2022-07-11 20:58   ` Tejun Heo
2022-07-11 21:11     ` Steven Rostedt
2022-07-12  5:42       ` Xuewen Yan
2022-07-12  5:57       ` Xuewen Yan
2022-07-13  3:02       ` Waiman Long
2022-07-12 12:57     ` Qais Yousef
2022-07-12 16:13       ` Tejun Heo
2022-07-12 17:14         ` Qais Yousef
2022-07-27 22:01         ` Peter Zijlstra
2022-07-27 22:05           ` Tejun Heo
2022-07-13  2:49     ` Waiman Long
2022-07-13  3:00       ` Tejun Heo
2022-07-20  7:45         ` Xuewen Yan
2022-07-27 20:09           ` Tejun Heo
2022-07-29  7:33             ` Xuewen Yan
2022-07-29  8:39               ` Qais Yousef
2022-07-29 19:59                 ` Tejun Heo
2022-08-09  2:02                   ` Xuewen Yan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220711074724.tbwefl42fpf2aq5a@vireshk-i7 \
    --to=viresh.kumar@linaro.org \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=ke.wang@unisoc.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mgorman@suse.de \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=vincent.guittot@linaro.org \
    --cc=xuewen.yan94@gmail.com \
    --cc=xuewen.yan@unisoc.com \
    --cc=xuewyan@foxmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®