From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752955AbcKHC6V (ORCPT ); Mon, 7 Nov 2016 21:58:21 -0500 Received: from LGEAMRELO11.lge.com ([156.147.23.51]:53644 "EHLO lgeamrelo11.lge.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752218AbcKHC6T (ORCPT ); Mon, 7 Nov 2016 21:58:19 -0500 X-Original-SENDERIP: 156.147.1.151 X-Original-MAILFROM: byungchul.park@lge.com X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Tue, 8 Nov 2016 11:54:25 +0900 From: Byungchul Park To: peterz@infradead.org, mingo@kernel.org Cc: tglx@linutronix.de, walken@google.com, boqun.feng@gmail.com, kirill@shutemov.name, linux-kernel@vger.kernel.org, linux-mm@kvack.org, iamjoonsoo.kim@lge.com, akpm@linux-foundation.org, npiggin@gmail.com Subject: Re: [REVISED DOC on v3] Crossrelease Lockdep Message-ID: <20161108025425.GY2279@X58A-UD3R> References: <1473759914-17003-1-git-send-email-byungchul.park@lge.com> <20161102054242.GT2279@X58A-UD3R> <20161103081813.GV2279@X58A-UD3R> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161103081813.GV2279@X58A-UD3R> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 03, 2016 at 05:18:13PM +0900, Byungchul Park wrote: > Hello Peterz, > > I tried to explain about what you asked me for. > I wonder if I did it exactly. But I hope so. > Please let me know if there's something more I need to add. Just to be sure, are you concerning about sync and propagation delay of memory contents including lock variables between cpus? IMHO, it makes no difference. It's a true dependence once the dependency is viewable by a cpu, which means anyway it actually happened. And please remind all locks related to crosslocks are serialized via proper memory barriers. I think this was already descibed in my document. Is there something I missed? Please let me know. Thank you, Byungchul > > Thank you, > Byungchul