All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Feng Tang <feng.tang@intel.com>
Cc: "Paul E. McKenney" <paul.mckenney@linaro.org>,
	Len Brown <len.brown@intel.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: Re: [Regression 3.4] tick_broadcast_mask is not restored after a CPU has been offline/onlined
Date: Mon, 30 Jul 2012 06:39:13 -0700	[thread overview]
Message-ID: <20120730133913.GK2556@linux.vnet.ibm.com> (raw)
In-Reply-To: <20120730151559.772d4055@feng-i7>

On Mon, Jul 30, 2012 at 03:15:59PM +0800, Feng Tang wrote:
> Hi All,
> 
> When I debugged a suspend/resume bug, I found that tick_broadcast_mask is not
> restored for a CPU after it is offline/onlined since kernel 3.4, while it's
> fine for 3.3.

Could you please try 3.5?

> Further check show it is caused by the commit 9505626d7bfe
>    ACPI: Fix unprotected smp_processor_id() in acpi_processor_cst_has_changed()
> 	
>     The acpi_processor_cst_has_changed() function is invoked from a
>     CPU_ONLINE or CPU_DEAD function, which might well execute on CPU 0
>     even though the CPU being hotplugged is some other CPU.  In addition,
>     acpi_processor_cst_has_changed() invokes smp_processor_id() without
>     protection, resulting in splats when onlining CPUs.
>     
>     This commit therefore changes the smp_processor_id() to pr->id, as is
>     used elsewhere in the code, for example, in acpi_processor_add().
>     
>     Signed-off-by: Paul E. McKenney <paul.mckenney@linaro.org>
> 
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index 0e8e2de..9e57b06 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -1159,8 +1159,7 @@ int acpi_processor_cst_has_changed(struct acpi_processor *pr)
>          * to make the code that updates C-States be called once.
>          */
> 
> -       if (smp_processor_id() == 0 &&
> -                       cpuidle_get_driver() == &acpi_idle_driver) {
> +       if (pr->id == 0 && cpuidle_get_driver() == &acpi_idle_driver) {
> 
>                 cpuidle_pause_and_lock();
>                 /* Protect against cpu-hotplug */
> 
> The root cause is acpi_processor_cst_has_changed() will also be called when
> cpu_up() is run on cpu 0 to boot up other cpu, this commit will prevent the
> following code be run for that cpu, which triggers some side effect like the
> broadcast_mask is not restored. 
> 
> I raise this problem up and I don't if revert is a good solution here.

Indeed, that would re-introduce the splats from unprotected use of
smp_processor_id().  :-(

							Thanx, Paul


       reply	other threads:[~2012-07-30 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120730151559.772d4055@feng-i7>
2012-07-30 13:39 ` Paul E. McKenney [this message]
2012-07-30 15:07   ` [Regression 3.4] tick_broadcast_mask is not restored after a CPU has been offline/onlined Feng Tang
2012-07-30 17:08     ` Paul E. McKenney
2012-07-30 17:42       ` Paul E. McKenney
2012-07-31  3:18         ` Feng Tang
2012-07-31  4:09           ` Paul E. McKenney

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=20120730133913.GK2556@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=feng.tang@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paul.mckenney@linaro.org \
    --cc=rjw@sisk.pl \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.