[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f2fe6d4-38bf-4feb-1d5e-e2705c333670@nvidia.com>
Date: Tue, 26 Jul 2016 10:23:02 +0100
From: Jon Hunter <jonathanh@...dia.com>
To: <rcochran@...utronix.de>
CC: Anna-Maria Gleixner <anna-maria@...utronix.de>,
LKML <linux-kernel@...r.kernel.org>,
Peter Zijlstra <peterz@...radead.org>,
"Ingo Molnar" <mingo@...nel.org>,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [patch 61/66] timers: Convert to hotplug state machine
On 25/07/16 21:46, rcochran@...utronix.de wrote:
> On Mon, Jul 25, 2016 at 05:35:43PM +0200, rcochran@...utronix.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
Powered by blists - more mailing lists