From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756098AbcGZJXL (ORCPT ); Tue, 26 Jul 2016 05:23:11 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:6903 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755006AbcGZJXI (ORCPT ); Tue, 26 Jul 2016 05:23:08 -0400 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Tue, 26 Jul 2016 02:20:28 -0700 Subject: Re: [patch 61/66] timers: Convert to hotplug state machine To: References: <20160711122450.923603742@linutronix.de> <20160711122535.775201614@linutronix.de> <7d37714e-b072-ee90-f14f-364f4fd01f0d@nvidia.com> <20160725153543.GB10939@linutronix.de> <20160725204648.GA22830@linutronix.de> CC: Anna-Maria Gleixner , LKML , Peter Zijlstra , "Ingo Molnar" , Sebastian Andrzej Siewior , "linux-tegra@vger.kernel.org" From: Jon Hunter Message-ID: <6f2fe6d4-38bf-4feb-1d5e-e2705c333670@nvidia.com> Date: Tue, 26 Jul 2016 10:23:02 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <20160725204648.GA22830@linutronix.de> X-Originating-IP: [10.26.11.53] X-ClientProxiedBy: UKMAIL102.nvidia.com (10.26.138.15) To UKMAIL101.nvidia.com (10.26.138.13) Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 25/07/16 21:46, rcochran@linutronix.de wrote: > On Mon, Jul 25, 2016 at 05:35:43PM +0200, rcochran@linutronix.de wrote: >> I see if I can find a tegra system to test with... > > I tried the tip:smp/hotplug branch under kvm x86_64, and I didn't see > any problems with suspend or hibernate, even with CONFIG_PREEMPT_NONE. > I'll see if I can get my hands on a tegra system tomorrow. Until > then, two questions: > > 1. The issue appears with suspend (echo mem > /sys/power/state), as > opposed to hibernate, right? Yes. I have been using rtcwake to test suspend with the following arguments ... # rtcwake -d rtc1 -m mem -s 3 > 2. CONFIG_PREEMPT_NONE is good, but CONFIG_PREEMPT is bad, right? The other way around. Cheers Jon -- nvpublic