From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qg0-f41.google.com (mail-qg0-f41.google.com [209.85.192.41]) by kanga.kvack.org (Postfix) with ESMTP id B8E596B006C for ; Mon, 11 May 2015 03:47:15 -0400 (EDT) Received: by qgej70 with SMTP id j70so63863200qge.2 for ; Mon, 11 May 2015 00:47:15 -0700 (PDT) Received: from mail-qk0-x22f.google.com (mail-qk0-x22f.google.com. [2607:f8b0:400d:c09::22f]) by mx.google.com with ESMTPS id 194si6764702qhs.8.2015.05.11.00.47.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 May 2015 00:47:15 -0700 (PDT) Received: by qkgx75 with SMTP id x75so81860719qkg.1 for ; Mon, 11 May 2015 00:47:14 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20150507064557.GA26928@july> <20150507154212.GA12245@htj.duckdns.org> <20150508152513.GB28439@htj.duckdns.org> Date: Mon, 11 May 2015 16:47:14 +0900 Message-ID: Subject: Re: [RFC PATCH] PM, freezer: Don't thaw when it's intended frozen processes From: Kyungmin Park Content-Type: text/plain; charset=UTF-8 Sender: owner-linux-mm@kvack.org List-ID: To: Tejun Heo Cc: linux-mm , Andrew Morton , "\\Rafael J. Wysocki\\" , David Rientjes , Johannes Weiner , Oleg Nesterov , Cong Wang , LKML , Linux PM list On Mon, May 11, 2015 at 1:28 PM, Kyungmin Park wrote: > On Sat, May 9, 2015 at 12:25 AM, Tejun Heo wrote: >> Hello, Kyungmin. >> >> On Fri, May 08, 2015 at 09:04:26AM +0900, Kyungmin Park wrote: >>> > I need to think more about it but as an *optimization* we can add >>> > freezing() test before actually waking tasks up during resume, but can >>> > you please clarify what you're seeing? >>> >>> The mobile application has life cycle and one of them is 'suspend' >>> state. it's different from 'pause' or 'background'. >>> if there are some application and enter go 'suspend' state. all >>> behaviors are stopped and can't do anything. right it's suspended. but >>> after system suspend & resume, these application is thawed and >>> running. even though system know it's suspended. >>> >>> We made some test application, print out some message within infinite >>> loop. when it goes 'suspend' state. nothing is print out. but after >>> system suspend & resume, it prints out again. that's not desired >>> behavior. and want to address it. >>> >>> frozen user processes should be remained as frozen while system >>> suspend & resume. >> >> Yes, they should and I'm not sure why what you're saying is happening >> because freezing() test done from the frozen tasks themselves should >> keep them in the freezer. Which kernel version did you test? Can you >> please verify it against a recent kernel? > > The kernel 3.10 is not working as expected, but right the latest > kernel is working correctly. Please ignore it. test is wrong and it's not working, see Krzysztof Mail. > > I see I'll check what's different and which are modified. > > Thank you, > Kyungmin Park -- 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