Re: [PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call()

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

Re: [PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call()

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

[PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call()

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

[PATCH] x86: remove redundant local_irq_enable() after cpuidle_idle_call()

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