public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Li.Wang" <Li.Wang@windriver.com>
To: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<x86@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call()
Date: Tue, 20 Aug 2013 10:21:44 +0800	[thread overview]
Message-ID: <5212D2B8.6090602@windriver.com> (raw)
In-Reply-To: <1376446800-3778-1-git-send-email-li.wang@windriver.com>

Hi All,

Anybody help me review this?

Thanks,
LiWang.

On 08/14/2013 10:20 AM, Li Wang wrote:
> When cpuidle_idle_call() return 0, it shows that linux system is using
> idle framwork driver. Now, local irq has already been enabled in
> cpuidle_idle_call(). So, it need not enable local irq again, when return 0.
>
> The code is introduced by commit:
> 97a5b81fa4d3a11dcdf224befc577f2e0abadc0b ("x86: Fix idle consolidation fallout")
> In that defect, it does not use idle framework driver, just call amd_e400_idle().
> That problem is that amd_e400_idle() does not enable irq.
>
> Signed-off-by: Li Wang <li.wang@windriver.com>
> ---
>   arch/x86/kernel/process.c |    2 --
>   1 file changed, 2 deletions(-)
>
> diff --git a/arch/x86/kernel/process.c b/arch/x86/kernel/process.c
> index 83369e5..cb55ee4 100644
> --- a/arch/x86/kernel/process.c
> +++ b/arch/x86/kernel/process.c
> @@ -300,8 +300,6 @@ void arch_cpu_idle(void)
>   {
>   	if (cpuidle_idle_call())
>   		x86_idle();
> -	else
> -		local_irq_enable();
>   }
>   
>   /*


      reply	other threads:[~2013-08-20  4:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-14  2:20 [PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call() Li Wang
2013-08-20  2:21 ` Li.Wang [this message]

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=5212D2B8.6090602@windriver.com \
    --to=li.wang@windriver.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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