From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f69.google.com (mail-wm0-f69.google.com [74.125.82.69]) by kanga.kvack.org (Postfix) with ESMTP id 136C86B02A8 for ; Tue, 27 Sep 2016 10:51:33 -0400 (EDT) Received: by mail-wm0-f69.google.com with SMTP id l138so10612744wmg.3 for ; Tue, 27 Sep 2016 07:51:33 -0700 (PDT) Received: from mail-wm0-x244.google.com (mail-wm0-x244.google.com. [2a00:1450:400c:c09::244]) by mx.google.com with ESMTPS id r4si2231604wmd.5.2016.09.27.07.51.31 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 27 Sep 2016 07:51:31 -0700 (PDT) Received: by mail-wm0-x244.google.com with SMTP id l132so1542585wmf.1 for ; Tue, 27 Sep 2016 07:51:31 -0700 (PDT) Date: Tue, 27 Sep 2016 16:51:29 +0200 From: Frederic Weisbecker Subject: Re: [PATCH v15 04/13] task_isolation: add initial support Message-ID: <20160927145128.GF6242@lerouge> References: <3f84f736-ed7f-adff-d5f0-4f7db664208f@mellanox.com> <20160927142219.GC6242@lerouge> <20160927143926.GQ2794@worktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160927143926.GQ2794@worktop> Sender: owner-linux-mm@kvack.org List-ID: To: Peter Zijlstra Cc: Andy Lutomirski , Chris Metcalf , Thomas Gleixner , "linux-doc@vger.kernel.org" , Christoph Lameter , Michal Hocko , Gilad Ben Yossef , Andrew Morton , Viresh Kumar , Linux API , Steven Rostedt , Ingo Molnar , Tejun Heo , Rik van Riel , Will Deacon , "Paul E. McKenney" , "linux-mm@kvack.org" , "linux-kernel@vger.kernel.org" , Catalin Marinas On Tue, Sep 27, 2016 at 04:39:26PM +0200, Peter Zijlstra wrote: > On Tue, Sep 27, 2016 at 04:22:20PM +0200, Frederic Weisbecker wrote: > > > The RCU context tracking doesn't take care of callbacks. It's only there > > to tell the RCU core whether the CPU runs code that may or may not run > > RCU read side critical sections. This is assumed by "kernel may use RCU, > > userspace can't". > > Userspace never can use the kernels RCU in any case. What you mean to > say is that userspace is treated like an idle CPU in that the CPU will > no longer be part of the RCU quescent state machine. > > The transition to userspace (as per context tracking) must ensure that > CPUs RCU state is 'complete', just like our transition to idle (mostly) > does. Exactly! -- 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: email@kvack.org