From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>
Subject: Re: [PATCH 1/2] sched/mm: add finish_switch_mm function
Date: Wed, 13 Nov 2013 12:49:13 +0100 [thread overview]
Message-ID: <20131113124913.005fcfe5@mschwide> (raw)
In-Reply-To: <20131113114143.GJ21461@twins.programming.kicks-ass.net>
On Wed, 13 Nov 2013 12:41:43 +0100
Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Nov 13, 2013 at 09:16:13AM +0100, Martin Schwidefsky wrote:
> > The switch_mm function is called with the task_lock and/or with
> > request queue lock. Add finish_switch_mm to allow an architecture
> > to execute some code after the mm has been switched but without
> > any locks held. One use case is the s390 architecture which will
> > use this to wait for the completion of TLB flush operations.
>
> This so reminds me of what finish_arch_post_lock_switch() was supposed
> to do. See commit: 01f23e1630d9 ("sched/arch: Introduce the
> finish_arch_post_lock_switch() scheduler callback").
>
> Now you hook into more places; but maybe you can Catalin can come up
> with something you both can use?
finish_task_switch() has the call to finish_arch_post_lock_switch(), but
idle_task_exit() and use_mm() do not have the call. If it is safe to add
finish_arch_post_lock_switch() there as well I could use it for s390.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next prev parent reply other threads:[~2013-11-13 11:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 8:16 [PATCH 0/2] sched: finish_switch_mm hook Martin Schwidefsky
2013-11-13 8:16 ` [PATCH 1/2] sched/mm: add finish_switch_mm function Martin Schwidefsky
2013-11-13 11:41 ` Peter Zijlstra
2013-11-13 11:49 ` Martin Schwidefsky [this message]
2013-11-13 12:19 ` Catalin Marinas
2013-11-13 16:05 ` Martin Schwidefsky
2013-11-13 17:03 ` Catalin Marinas
2013-11-14 8:00 ` Martin Schwidefsky
2013-11-13 8:16 ` [PATCH 2/2] s390/mm,tlb: race of lazy TLB flush vs. recreation of TLB entries Martin Schwidefsky
2013-11-13 16:16 ` Catalin Marinas
2013-11-14 8:10 ` Martin Schwidefsky
2013-11-14 13:22 ` Catalin Marinas
2013-11-14 16:33 ` Martin Schwidefsky
2013-11-15 10:44 ` Catalin Marinas
2013-11-15 11:10 ` Martin Schwidefsky
2013-11-15 11:17 ` Martin Schwidefsky
2013-11-15 11:57 ` Catalin Marinas
2013-11-15 13:29 ` Martin Schwidefsky
2013-11-15 13:46 ` Catalin Marinas
2013-11-18 8:11 ` Martin Schwidefsky
2013-11-15 9:13 ` Martin Schwidefsky
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=20131113124913.005fcfe5@mschwide \
--to=schwidefsky@de.ibm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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).