Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754350AbbGFLGt (ORCPT ); Mon, 6 Jul 2015 07:06:49 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:43989 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753846AbbGFLGr (ORCPT ); Mon, 6 Jul 2015 07:06:47 -0400 Date: Mon, 6 Jul 2015 13:06:45 +0200 From: Pavel Machek To: "Rafael J. Wysocki" Cc: Alan Stern , Dave Chinner , Len Brown , Henrique de Moraes Holschuh , One Thousand Gnomes , Linux PM list , "linux-kernel@vger.kernel.org" , Len Brown Subject: Re: [PATCH 1/1] suspend: delete sys_sync() Message-ID: <20150706110645.GC381@amd> References: <2293886.L6VJGgjdDp@vostro.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2293886.L6VJGgjdDp@vostro.rjw.lan> User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1952 Lines: 47 On Mon 2015-07-06 01:28:20, Rafael J. Wysocki wrote: > On Saturday, July 04, 2015 10:19:55 AM Alan Stern wrote: > > On Sat, 4 Jul 2015, Rafael J. Wysocki wrote: > > > > > The only argument against dropping sys_sync() from the suspend code path > > > I've seen in this thread that I entirely agree with is that it may lead to > > > regressions, because we've done it practically forever and it may hide latent > > > bugs somewhere in block drivers etc. Dropping it, though, is the only way > > > to see those bugs, if any, and if we want to ever fix them, we need to see > > > them. That's why I think that it may be a good idea to allow people to > > > drop it if they are willing to accept some extra risk (via the kernel > > > command line, for example). > > > > I'd be perfectly happy to have the sync selectable at runtime, one way > > or another. The three most reasonable options seem to be: > > > > kernel command line > > > > sysfs file > > > > sysctl setting > > > > The command line is less flexible (it can't be changed after booting). > > Either of the other two would be fine with me. > > We'll probably use a sysfs file (possibly plus a Kconfig option to set the > boot time default). Android people can already do sync-less s2ram using existing interface. IMO they should just do it. In any case, sysfs file + Kconfig is an overkill. We already have too many Kconfig options. There's not a single Android phone supported by mainline kernel. I'm sure they have bigger problems than Android setting default sysfs values... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/