From: "Li, Aubrey" <aubrey.li@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Brown, Len" <len.brown@intel.com>,
"alan@linux.intel.com" <alan@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org,
"linux-pm@vger.kernel.org >> Linux PM list"
<linux-pm@vger.kernel.org>
Subject: Re: [RFC/PATCH] PM / Sleep: Timer quiesce in freeze state
Date: Tue, 28 Oct 2014 12:39:53 +0800 [thread overview]
Message-ID: <544F1E19.5030606@linux.intel.com> (raw)
In-Reply-To: <20141024153656.GM12706@worktop.programming.kicks-ass.net>
On 2014/10/24 23:36, Peter Zijlstra wrote:
>> +
>> +static void freezer_idle(int cpu)
>> +{
>> + struct cpuidle_device *dev = __this_cpu_read(cpuidle_devices);
>> + struct cpuidle_driver *drv = cpuidle_get_cpu_driver(dev);
>> +
>> + stop_critical_timings();
>> +
>> + while (suspend_freeze_wake == -1) {
>> + int next_state;
>> +
>> + /*
>> + * interrupt must be disabled before cpu enters idle
>> + */
>> + local_irq_disable();
>> +
>> + next_state = cpuidle_select(drv, dev);
>> + if (next_state < 0) {
>> + arch_cpu_idle();
>> + continue;
>> + }
>> + /*
>> + * cpuidle_enter will return with interrupt enabled
>> + */
>> + cpuidle_enter(drv, dev, next_state);
>> + }
>> +
>> + if (suspend_freeze_wake == cpu)
>> + kick_all_cpus_sync();
>> +
>
> So I disabled IRQs here
>
>> + start_critical_timings();
>> +}
>> +
>> +static void freezer_resume_tk(int cpu)
>> +{
>> + if (tick_do_timer_cpu != cpu)
>> + return;
>> +
>> cpuidle_pause();
>> cpuidle_use_deepest_state(false);
>> +
>
> Such that they would still be disabled here
>
>> + local_irq_disable();
>> + timekeeping_resume();
>> + local_irq_enable();
>> +}
>> +
>> +static void freezer_resume_clkevt(int cpu)
>> +{
>> + if (tick_do_timer_cpu == cpu)
>> + return;
>> +
>> + touch_softlockup_watchdog();
>> + clockevents_notify(CLOCK_EVT_NOTIFY_RESUME, NULL);
>
> And here.
>
>> + local_irq_disable();
>> + hrtimers_resume();
>> + local_irq_enable();
>> +}
>> +
>> +typedef void (*freezer_fn)(int);
>> +
>> +static freezer_fn freezer_func[FREEZER_EXIT] = {
>> + NULL,
>> + freezer_pick_tk,
>> + freezer_suspend_clkevt,
>> + freezer_suspend_tk,
>> + freezer_idle,
>> + freezer_resume_tk,
>> + freezer_resume_clkevt,
>> +};
>
> Because this is a stop_machine callback, which are nominally run with
> IRQs disabled.
>
>> +static int freezer_stopper_fn(void *arg)
>> +{
>> + struct freezer_data *fd = arg;
>> + enum freezer_state state = FREEZER_NONE;
>> + int cpu = smp_processor_id();
>> +
>> + do {
>> + cpu_relax();
>> + if (fd->state != state) {
>> + state = fd->state;
>> + if (freezer_func[state])
>> + (*freezer_func[state])(cpu);
>> + ack_state(fd);
>> + }
>> + } while (fd->state != FREEZER_EXIT);
>> + return 0;
>> +}
>
> Now I suppose the problem is with cpu_pause() which needs IPIs to
> complete?
Yes, cpu_pause() will invoke smp IPI functions which need interrupt is
enabled. So I changed irq ops like above. Actually, I have an early
version to move cpuidle_pause()/cpuidle_resume() out of stop_machine(),
that might be a better solution?
Thanks,
-Aubrey
next prev parent reply other threads:[~2014-10-28 4:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 15:15 [RFC/PATCH] PM / Sleep: Timer quiesce in freeze state Li, Aubrey
2014-10-24 15:36 ` Peter Zijlstra
2014-10-27 6:27 ` Li, Aubrey
2014-10-27 7:28 ` Peter Zijlstra
2014-10-28 4:32 ` Li, Aubrey
2014-10-28 8:29 ` Peter Zijlstra
2014-10-28 22:46 ` Li, Aubrey
2014-10-29 8:21 ` Peter Zijlstra
2014-10-29 15:09 ` Li, Aubrey
2014-10-27 7:44 ` Peter Zijlstra
2014-10-28 7:52 ` Li, Aubrey
2014-10-28 8:25 ` Peter Zijlstra
2014-10-28 23:22 ` Li, Aubrey
2014-10-29 8:24 ` Peter Zijlstra
2014-10-30 2:58 ` [PATCH v2] " Li, Aubrey
2014-11-08 2:05 ` Rafael J. Wysocki
2014-11-10 11:49 ` Peter Zijlstra
2014-11-12 21:09 ` Thomas Gleixner
2014-11-13 1:37 ` Peter Zijlstra
2014-11-13 2:20 ` Li, Aubrey
2014-11-13 9:19 ` Thomas Gleixner
2014-11-13 10:50 ` Li, Aubrey
2014-11-13 9:10 ` Thomas Gleixner
2014-11-13 10:47 ` Li, Aubrey
2014-11-13 13:06 ` Thomas Gleixner
2014-11-14 7:58 ` Li, Aubrey
2014-10-28 4:39 ` Li, Aubrey [this message]
2014-10-28 8:25 ` [RFC/PATCH] " Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=544F1E19.5030606@linux.intel.com \
--to=aubrey.li@linux.intel.com \
--cc=alan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).