public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	linux-api <linux-api@vger.kernel.org>,
	Andy Lutomirski <luto@kernel.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Boqun Feng <boqun.feng@gmail.com>, Andrew Hunter <ahh@google.com>,
	maged michael <maged.michael@gmail.com>,
	Avi Kivity <avi@scylladb.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Dave Watson <davejwatson@fb.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrea Parri <parri.andrea@gmail.com>,
	"Russell King, ARM Linux" <linux@armlinux.org.uk>,
	Greg Hackmann <ghackmann@google.com>,
	Will Deacon <will.deacon@arm.com>, David Sehr <sehr@google.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	x86 <x86@kernel.org>, linux-arch <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 08/11] membarrier: Provide core serializing command (v2)
Date: Mon, 29 Jan 2018 18:36:05 +0000 (UTC)	[thread overview]
Message-ID: <485936677.11601.1517250965043.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <20180129181529.GG2295@hirez.programming.kicks-ass.net>

----- On Jan 29, 2018, at 1:15 PM, Peter Zijlstra peterz@infradead.org wrote:

> On Mon, Jan 29, 2018 at 07:04:14PM +0100, Peter Zijlstra wrote:
>> On Tue, Jan 23, 2018 at 10:57:30AM -0500, Mathieu Desnoyers wrote:
>> > diff --git a/kernel/sched/core.c b/kernel/sched/core.c
>> > index f38c4c7e256a..041893128f51 100644
>> > --- a/kernel/sched/core.c
>> > +++ b/kernel/sched/core.c
>> > @@ -2662,9 +2662,13 @@ static struct rq *finish_task_switch(struct task_struct
>> > *prev)
>> >  	 * thread, mmdrop()'s implicit full barrier is required by the
>> >  	 * membarrier system call, because the current active_mm can
>> >  	 * become the current mm without going through switch_mm().
>> > +	 * membarrier also requires a core serializing instruction
>> > +	 * before going back to user-space after storing to rq->curr.
>> >  	 */
>> > -	if (mm)
>> > +	if (mm) {
>> > +		membarrier_mm_sync_core_before_usermode(mm);
>> >  		mmdrop(mm);
>> > +	}
>> 
>> *confused*, when we switch from process A to process B, context_switch()
>> will not set rq->prev_mm and the above mm will be NULL and we'll not
>> pass through your_function_names_are_waaay_too_long and we'll not get
>> cookies.
>> 
>> And if there's anything more complicated going on, the comment/changelog
>> are not adequate.
> 
> Aaah, its the case where we do not pass through switch_mm(), the partial
> comment got to me. I only realized after reading the next patch.

Indeed, if we read the entire comment, it's made clear that this case is for
when switch_mm is not invoked, where the current mm is changed without going
through switch_mm(), when scheduling between uthread->kthread->uthread for
instance.

        /*
         * When transitioning from a kernel thread to a userspace
         * thread, mmdrop()'s implicit full barrier is required by the
         * membarrier system call, because the current active_mm can
         * become the current mm without going through switch_mm().
         * membarrier also requires a core serializing instruction
         * before going back to user-space after storing to rq->curr.
         */

Is there something I should improve in the wording of this added
sentence to make it clearer ?

Thanks,

Mathieu


> 
>> >  	if (unlikely(prev_state == TASK_DEAD)) {
>> >  		if (prev->sched_class->task_dead)
>> >  			prev->sched_class->task_dead(prev);
>> 

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2018-01-29 18:35 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-23 15:57 [PATCH for 4.16 00/11] membarrier updates for 4.16 Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 01/11] membarrier: selftest: Test private expedited cmd (v2) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 02/11] powerpc: membarrier: Skip memory barrier in switch_mm() (v7) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 03/11] membarrier: Document scheduler barrier requirements (v5) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 04/11] membarrier: provide GLOBAL_EXPEDITED command (v3) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 05/11] membarrier: selftest: Test global expedited cmd (v2) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 06/11] Introduce sync_core_before_usermode (v2) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 07/11] x86: Implement sync_core_before_usermode (v3) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 08/11] membarrier: Provide core serializing command (v2) Mathieu Desnoyers
2018-01-29 18:04   ` Peter Zijlstra
2018-01-29 18:15     ` Peter Zijlstra
2018-01-29 18:36       ` Mathieu Desnoyers [this message]
2018-01-29 19:09         ` Peter Zijlstra
2018-01-29 19:20           ` Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 09/11] membarrier: x86: Provide core serializing command (v4) Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 10/11] membarrier: arm64: Provide core serializing command Mathieu Desnoyers
2018-01-23 15:57 ` [PATCH 11/11] membarrier: selftest: Test private expedited sync core cmd Mathieu Desnoyers
2018-01-29 16:02 ` [PATCH for 4.16 00/11] membarrier updates for 4.16 Mathieu Desnoyers
2018-01-29 17:40 ` Linus Torvalds
2018-02-05 16:33   ` Ingo Molnar
2018-02-05 17:23     ` Linus Torvalds
2018-02-05 18:33       ` Ingo Molnar
2018-02-05 18:53       ` Mathieu Desnoyers
2018-02-05 19:49         ` Ingo Molnar
2018-02-05 19:54         ` Linus Torvalds
2018-01-29 19:13 ` Peter Zijlstra

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=485936677.11601.1517250965043.JavaMail.zimbra@efficios.com \
    --to=mathieu.desnoyers@efficios.com \
    --cc=ahh@google.com \
    --cc=avi@scylladb.com \
    --cc=benh@kernel.crashing.org \
    --cc=boqun.feng@gmail.com \
    --cc=davejwatson@fb.com \
    --cc=ghackmann@google.com \
    --cc=hpa@zytor.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=luto@kernel.org \
    --cc=maged.michael@gmail.com \
    --cc=mingo@redhat.com \
    --cc=mpe@ellerman.id.au \
    --cc=parri.andrea@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=sehr@google.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=will.deacon@arm.com \
    --cc=x86@kernel.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