From: Thomas Gleixner <tglx@linutronix.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Andrey Ryabinin <aryabinin@virtuozzo.com>,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch V2 1/2] mm: swap: Provide lru_add_drain_all_cpuslocked()
Date: Tue, 4 Jul 2017 14:35:59 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1707041434380.9000@nanos> (raw)
In-Reply-To: <b2522a26-334b-c66e-4cca-c9eeb4aa6f93@suse.cz>
On Tue, 4 Jul 2017, Vlastimil Babka wrote:
> >
> > -void lru_add_drain_all(void)
> > +void lru_add_drain_all_cpuslocked(void)
> > {
> > static DEFINE_MUTEX(lock);
> > static struct cpumask has_work;
> > @@ -701,7 +701,6 @@ void lru_add_drain_all(void)
> > return;
> >
> > mutex_lock(&lock);
> > - get_online_cpus();
>
> Is there a an assertion check that we are locked, that could be put in
> e.g. VM_WARN_ON_ONCE()?
There is a lockdep assertion lockdep_assert_cpus_held() which could be
used. Forgot to add it.
Thanks,
tglx
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-07-04 12:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 9:32 [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock Thomas Gleixner
2017-07-04 9:32 ` [patch V2 1/2] mm: swap: Provide lru_add_drain_all_cpuslocked() Thomas Gleixner
2017-07-04 10:58 ` Michal Hocko
2017-07-04 12:48 ` Thomas Gleixner
2017-07-04 12:52 ` Michal Hocko
2017-07-04 12:07 ` Vlastimil Babka
2017-07-04 12:35 ` Thomas Gleixner [this message]
2017-07-04 9:32 ` [patch V2 2/2] mm/memory-hotplug: Switch locking to a percpu rwsem Thomas Gleixner
2017-07-04 10:59 ` Michal Hocko
2017-07-04 12:10 ` Vlastimil Babka
2017-07-04 12:49 ` Thomas Gleixner
2017-07-04 15:01 ` Davidlohr Bueso
2017-07-04 15:22 ` Davidlohr Bueso
2017-07-04 15:32 ` Thomas Gleixner
2017-07-04 15:42 ` Davidlohr Bueso
2017-07-05 21:53 ` [patch V2 0/2] mm/memory_hotplug: Cure potential deadlocks vs. cpu hotplug lock Andrew Morton
2017-07-06 6:34 ` Thomas Gleixner
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=alpine.DEB.2.20.1707041434380.9000@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=aryabinin@virtuozzo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.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;
as well as URLs for NNTP newsgroup(s).