RE: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

> >> Reviewed-by: Andy Shevchenko > >> Reviewed-by: Koul, Vinod > > > A previous version of this has been applied and I don't see any differences > > in the code changes. > > AFAIR only tags (above) had been extended in v3. Thanks. Yes,

RE: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

> >> Reviewed-by: Andy Shevchenko > >> Reviewed-by: Koul, Vinod > > > A previous version of this has been applied and I don't see any differences > > in the code changes. > > AFAIR only tags (above) had been extended in v3. Thanks. Yes, for v3 no change in code, and only tags "Reviewed-by"

RE: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Thursday, May 4, 2017 6:16 PM Daniel Lezcano wrote: > > > > preempt_disable(); > > dev = cpuidle_get_device(); > > - dev->use_deepest_state = enable; > > + if (dev) > > + dev->use_deepest_state = enable; > > > This change is acceptable as a hot fix but the question is 'why

RE: [PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

On Thursday, May 4, 2017 6:16 PM Daniel Lezcano wrote: > > > > preempt_disable(); > > dev = cpuidle_get_device(); > > - dev->use_deepest_state = enable; > > + if (dev) > > + dev->use_deepest_state = enable; > > > This change is acceptable as a hot fix but the question is 'why

[PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state selection") Signed-off-by: Li, Fei <fei...@intel.com> Tested-by: Shi, Feng <fengx@intel.com> Reviewed-by: Andy Shevchenko <andriy.shevche...@linux.intel.com> Reviewed-by: Koul, Vinod <vinod.k...@

[PATCH V3] cpuidle: check dev before usage in cpuidle_use_deepest_state

Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state selection") Signed-off-by: Li, Fei Tested-by: Shi, Feng Reviewed-by: Andy Shevchenko Reviewed-by: Koul, Vinod --- drivers/cpuidle/cpuidle.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drive

[PATCH V2] cpuidle: check dev before usage in cpuidle_use_deepest_state

Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state selection") Signed-off-by: Li, Fei <fei...@intel.com> Tested-by: Shi, Feng <fengx@intel.com> --- drivers/cpuidle/cpuidle.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/cpuid

[PATCH V2] cpuidle: check dev before usage in cpuidle_use_deepest_state

Fixes: bb8313b603eb8 ("cpuidle: Allow enforcing deepest idle state selection") Signed-off-by: Li, Fei Tested-by: Shi, Feng --- drivers/cpuidle/cpuidle.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/cpuidle/cpuidle.c b/drivers/cpuidle/cpuidle.c ind

[tip:x86/reboot] reboot: Allow specifying warm/ cold reset for CF9 boot type

Commit-ID: 16c21ae5ca636cfd38e581ebcf709c49d78ea56d Gitweb: http://git.kernel.org/tip/16c21ae5ca636cfd38e581ebcf709c49d78ea56d Author: Li Fei AuthorDate: Wed, 21 Aug 2013 16:13:57 +0800 Committer: Ingo Molnar CommitDate: Wed, 25 Sep 2013 19:33:22 +0200 reboot: Allow specifying warm

[tip:x86/reboot] reboot: Allow specifying warm/ cold reset for CF9 boot type

Commit-ID: 16c21ae5ca636cfd38e581ebcf709c49d78ea56d Gitweb: http://git.kernel.org/tip/16c21ae5ca636cfd38e581ebcf709c49d78ea56d Author: Li Fei fei...@intel.com AuthorDate: Wed, 21 Aug 2013 16:13:57 +0800 Committer: Ingo Molnar mi...@kernel.org CommitDate: Wed, 25 Sep 2013 19:33:22 +0200

[tip:x86/reboot] reboot: Allow specifying warm/ cold reset for CF9 boot type

Commit-ID: 02020dae966ae71e8010ecbd04eb847ad0d53669 Gitweb: http://git.kernel.org/tip/02020dae966ae71e8010ecbd04eb847ad0d53669 Author: Li Fei AuthorDate: Wed, 21 Aug 2013 16:13:57 +0800 Committer: H. Peter Anvin CommitDate: Tue, 10 Sep 2013 08:56:02 -0700 reboot: Allow specifying warm

[tip:x86/reboot] reboot: Allow specifying warm/ cold reset for CF9 boot type

Commit-ID: 02020dae966ae71e8010ecbd04eb847ad0d53669 Gitweb: http://git.kernel.org/tip/02020dae966ae71e8010ecbd04eb847ad0d53669 Author: Li Fei fei...@intel.com AuthorDate: Wed, 21 Aug 2013 16:13:57 +0800 Committer: H. Peter Anvin h...@linux.intel.com CommitDate: Tue, 10 Sep 2013 08:56:02

RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type

> Subject: RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type > > The thing is that the existing "warm" and "cold" means something different, I > believe (skip post vs do post.) It is possible it just works, but it would > be good to > know which platforms or works on. > >

[PATCH V2] reboot: perform warm/cold reset correctly for CF9 type

, write 0x06 to port 0xCF9; For cold reset, write 0x0E to port 0xCF9. From: Liu Chuansheng Signed-off-by: Li Fei --- arch/x86/kernel/reboot.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index 563ed91..ca42f63

RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type

> Careful. This is a very different definition of warm vs cold boot used > elsewhere. We have tested both warm and cold reboot on our x86 platform, and it works well. Besides with commit, the expected warm and reboot type can be specified through command line. > >Looks good, but please

RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type

Careful. This is a very different definition of warm vs cold boot used elsewhere. We have tested both warm and cold reboot on our x86 platform, and it works well. Besides with commit, the expected warm and reboot type can be specified through command line. Looks good, but please introduce a

[PATCH V2] reboot: perform warm/cold reset correctly for CF9 type

, write 0x06 to port 0xCF9; For cold reset, write 0x0E to port 0xCF9. From: Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- arch/x86/kernel/reboot.c |7 +-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/reboot.c b/arch/x86

RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type

Subject: RE: [PATCH] reboot: perform warm/cold reset correctly for CF9 type The thing is that the existing warm and cold means something different, I believe (skip post vs do post.) It is possible it just works, but it would be good to know which platforms or works on. Also, why do you

[PATCH] irq: add irq handler function name in ftrace

At present, irq handler function name is not printed out when irq_handler_entry is added into trace event, which is inconvenient for debugging. In order to improve the debugging efficiency, print out the handler function name in irq_handler_entry. Signed-off-by: Li Fei Acked-by: Liu Chuansheng

[PATCH] reboot: perform warm/cold reset correctly for CF9 type

, write 0x06 to port 0xCF9; For cold reset, write 0x0E to port 0xCF9. From: Liu Chuansheng Signed-off-by: Li Fei --- arch/x86/kernel/reboot.c |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/reboot.c b/arch/x86/kernel/reboot.c index 563ed91..6e06299

[PATCH] reboot: perform warm/cold reset correctly for CF9 type

, write 0x06 to port 0xCF9; For cold reset, write 0x0E to port 0xCF9. From: Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- arch/x86/kernel/reboot.c |9 +++-- 1 files changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/x86/kernel/reboot.c b/arch/x86

[PATCH] irq: add irq handler function name in ftrace

At present, irq handler function name is not printed out when irq_handler_entry is added into trace event, which is inconvenient for debugging. In order to improve the debugging efficiency, print out the handler function name in irq_handler_entry. Signed-off-by: Li Fei fei...@intel.com Acked

[tip:perf/urgent] x86: Eliminate irq_mis_count counted in arch_irq_stat

Commit-ID: f7b0e1055574ce06ab53391263b4e205bf38daf3 Gitweb: http://git.kernel.org/tip/f7b0e1055574ce06ab53391263b4e205bf38daf3 Author: Li Fei AuthorDate: Fri, 26 Apr 2013 20:50:11 +0800 Committer: Ingo Molnar CommitDate: Tue, 30 Apr 2013 10:56:37 +0200 x86: Eliminate irq_mis_count

[tip:perf/urgent] x86: Eliminate irq_mis_count counted in arch_irq_stat

Commit-ID: f7b0e1055574ce06ab53391263b4e205bf38daf3 Gitweb: http://git.kernel.org/tip/f7b0e1055574ce06ab53391263b4e205bf38daf3 Author: Li Fei fei...@intel.com AuthorDate: Fri, 26 Apr 2013 20:50:11 +0800 Committer: Ingo Molnar mi...@kernel.org CommitDate: Tue, 30 Apr 2013 10:56:37 +0200

[PATCH V2] x86: eliminate irq_mis_count counted in arch_irq_stat

With current implementation, kstat_cpu(cpu).irqs_sum is also increased in case of irq_mis_count increment. So there is no need to count irq_mis_count in arch_irq_stat, otherwise irq_mis_count will be counted twice in the sum of /proc/stat. Reported-by: Liu Chuansheng Signed-off-by: Li Fei

RE: [PATCH] x86: eliminate irq_mis_count counted in arch_irq_stat

> > Signed-off-by: Liu Chuansheng > > Signed-off-by: Li Fei > > The patch looks good, but this is not a valid signoff sequence. If Liu > Chuansheng wrote this patch then his From: line should be included. If he > acked it, then it should be added as Acked-by. > Hel

[PATCH] x86: eliminate irq_mis_count counted in arch_irq_stat

With current implementation, kstat_cpu(cpu).irqs_sum is also increased in case of irq_mis_count increment. So there is no need to count irq_mis_count in arch_irq_stat, otherwise irq_mis_count will be counted twice in the sum of /proc/stat. Signed-off-by: Liu Chuansheng Signed-off-by: Li Fei

[PATCH] x86: eliminate irq_mis_count counted in arch_irq_stat

Signed-off-by: Li Fei fei...@intel.com --- arch/x86/kernel/irq.c |4 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c index e4595f1..84b7789 100644 --- a/arch/x86/kernel/irq.c +++ b/arch/x86/kernel/irq.c @@ -165,10 +165,6 @@ u64

RE: [PATCH] x86: eliminate irq_mis_count counted in arch_irq_stat

Signed-off-by: Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com The patch looks good, but this is not a valid signoff sequence. If Liu Chuansheng wrote this patch then his From: line should be included. If he acked it, then it should be added as Acked

[PATCH V2] x86: eliminate irq_mis_count counted in arch_irq_stat

Signed-off-by: Li Fei fei...@intel.com Acked-by: Liu Chuansheng chuansheng@intel.com --- arch/x86/kernel/irq.c |4 1 files changed, 0 insertions(+), 4 deletions(-) diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c index e4595f1..84b7789 100644 --- a/arch/x86/kernel/irq.c +++ b

[PATCH 2/5 V2] mmc: core: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put_noidle in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/mmc/core

RE: [PATCH 2/5] mmc: core: call pm_runtime_put_sync in pm_runtime_get_sync failed case

> > Hi Li, > > On Thu, Feb 28, 2013 at 9:44 AM, Li Fei wrote: > > Even in failed case of pm_runtime_get_sync, the usage_count > > is incremented. In order to keep the usage_count with correct > > value and runtime power management to behave correctly, call > >

RE: [PATCH 2/5] mmc: core: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Hi Li, On Thu, Feb 28, 2013 at 9:44 AM, Li Fei fei...@intel.com wrote: Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync

[PATCH 2/5 V2] mmc: core: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put_noidle in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

[PATCH 5/5 V2] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

in pm_runtime_get_sync failed case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/hwspinlock/hwspinlock_core.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/hwspinlock/hwspinlock_core.c b/drivers/hwspinlock/hwspinlock_core.c index db713c0..461a0d7

RE: [PATCH 5/5] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

> -Original Message- > From: Rafael J. Wysocki [mailto:r...@sisk.pl] > Sent: Friday, April 05, 2013 7:42 PM > To: Ohad Ben-Cohen; Liu, Chuansheng > Cc: Li, Fei; linux-kernel@vger.kernel.org > Subject: Re: [PATCH 5/5] hwspinlock/core: call pm_runtime_put in > pm_runtime

RE: [PATCH 5/5] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

-Original Message- From: Rafael J. Wysocki [mailto:r...@sisk.pl] Sent: Friday, April 05, 2013 7:42 PM To: Ohad Ben-Cohen; Liu, Chuansheng Cc: Li, Fei; linux-kernel@vger.kernel.org Subject: Re: [PATCH 5/5] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

[PATCH 5/5 V2] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

in pm_runtime_get_sync failed case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- drivers/hwspinlock/hwspinlock_core.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/hwspinlock/hwspinlock_core.c b/drivers/hwspinlock

RE: [PATCH] pm: print the name of failed suspend function for platform device

currently such information is printed with level KERN_ERR, and can be tuned through console_loglevel to avoid the possible impact to end user. Do you think it make sense? Thanks and Regards, Li Fei > greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

[PATCH] pm: print the name of failed suspend function for platform device

: platform_pm_suspend(): power_suspend+0x0/0x30 returns -11 pm_op(): platform_pm_suspend+0x0/0x80 returns -11 PM: Device power.0 failed to suspend: error -11 Signed-off-by: liu chuansheng Signed-off-by: Li Fei --- drivers/base/platform.c | 19 +++ 1 files changed, 15 insertions(+), 4

[PATCH] pm: print the name of failed suspend function for platform device

: platform_pm_suspend(): power_suspend+0x0/0x30 returns -11 pm_op(): platform_pm_suspend+0x0/0x80 returns -11 PM: Device power.0 failed to suspend: error -11 Signed-off-by: liu chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- drivers/base/platform.c | 19

RE: [PATCH] pm: print the name of failed suspend function for platform device

the possible impact to end user. Do you think it make sense? Thanks and Regards, Li Fei greg k-h -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read

[PATCH 4/5 V3] usb: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync/noidle) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/usb

[PATCH 4/5 V3] usb: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync/noidle) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/usb

[PATCH 4/5 V2] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/usb/core

RE: [PATCH 4/5] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

> -Original Message- > From: Lan, Tianyu > Sent: Thursday, February 28, 2013 4:37 PM > To: Li, Fei; st...@rowland.harvard.edu > Cc: gre...@linuxfoundation.org; sarah.a.sh...@linux.intel.com; r...@sisk.pl; > linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Liu, Ch

[PATCH 5/5] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

in pm_runtime_get_sync failed case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/hwspinlock/hwspinlock_core.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/hwspinlock/hwspinlock_core.c b/drivers/hwspinlock/hwspinlock_core.c index db713c0..5a5076d

[PATCH 5/5] hwspinlock/core: call pm_runtime_put in pm_runtime_get_sync failed case

in pm_runtime_get_sync failed case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- drivers/hwspinlock/hwspinlock_core.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/hwspinlock/hwspinlock_core.c b/drivers/hwspinlock

RE: [PATCH 4/5] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

-Original Message- From: Lan, Tianyu Sent: Thursday, February 28, 2013 4:37 PM To: Li, Fei; st...@rowland.harvard.edu Cc: gre...@linuxfoundation.org; sarah.a.sh...@linux.intel.com; r...@sisk.pl; linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Liu, Chuansheng Subject: Re

[PATCH 4/5 V2] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

[PATCH 4/5 V3] usb: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

-by: Li Fei fei...@intel.com --- drivers/usb/core/hub.c |3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/drivers/usb/core/hub.c b/drivers/usb/core/hub.c index 5480352..4a6c055 100644 --- a/drivers/usb/core/hub.c +++ b/drivers/usb/core/hub.c @@ -3148,12 +3148,13 @@ int

[PATCH 4/5 V3] usb: call pm_runtime_put_noidle in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync/noidle) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li

[PATCH 4/5] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/usb/core

[PATCH 3/5] wl1251: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/net

[PATCH 2/5] mmc: core: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/mmc/core

[PATCH 1/5] regmap: irq: call pm_runtime_put in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng Signed-off-by: Li Fei --- drivers/base/regmap

[PATCH 1/5] regmap: irq: call pm_runtime_put in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

[PATCH 2/5] mmc: core: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

[PATCH 3/5] wl1251: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

[PATCH 4/5] usb: call pm_runtime_put_sync in pm_runtime_get_sync failed case

Even in failed case of pm_runtime_get_sync, the usage_count is incremented. In order to keep the usage_count with correct value and runtime power management to behave correctly, call pm_runtime_put(_sync) in such case. Signed-off-by Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei

RE: [PATCH] freezer: configure user space process frozen along with kernel threads

> -Original Message- > From: Cyrill Gorcunov [mailto:gorcu...@gmail.com] On Behalf Of Cyrill > Gorcunov > Sent: Wednesday, February 20, 2013 5:05 PM > To: Li, Fei > Cc: pa...@ucw.cz; r...@sisk.pl; Brown, Len; mi...@redhat.com; > pet...@infradead.org; a...@li

RE: [PATCH] freezer: configure user space process frozen along with kernel threads

-Original Message- From: Cyrill Gorcunov [mailto:gorcu...@gmail.com] On Behalf Of Cyrill Gorcunov Sent: Wednesday, February 20, 2013 5:05 PM To: Li, Fei Cc: pa...@ucw.cz; r...@sisk.pl; Brown, Len; mi...@redhat.com; pet...@infradead.org; a...@linux-foundation.org; v

RE: Getting rid of freezer for suspend [was Re: [fuse-devel] [PATCH] fuse: make fuse daemon frozen along with kernel threads]

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Tuesday, February 19, 2013 6:47 PM > To: Rafael J. Wysocki > Cc: Li, Fei; Miklos Szeredi; Goswin von Brederlow; Brown, Len; > mi...@redhat.com; pet...@infradead.org; Wang, Biao; > linux...@vge

[PATCH] freezer: configure user space process frozen along with kernel threads

, and writing 0 to it will make the process to be frozen together with user space processes. Signed-off-by: Liu Chuansheng Signed-off-by: Wang Biao Signed-off-by: Li Fei --- fs/proc/base.c | 70 +++ include/linux/freezer.h |6 include

[PATCH] freezer: configure user space process frozen along with kernel threads

, and writing 0 to it will make the process to be frozen together with user space processes. Signed-off-by: Liu Chuansheng chuansheng@intel.com Signed-off-by: Wang Biao biao.w...@intel.com Signed-off-by: Li Fei fei...@intel.com --- fs/proc/base.c | 70

RE: Getting rid of freezer for suspend [was Re: [fuse-devel] [PATCH] fuse: make fuse daemon frozen along with kernel threads]

-Original Message- From: Pavel Machek [mailto:pa...@ucw.cz] Sent: Tuesday, February 19, 2013 6:47 PM To: Rafael J. Wysocki Cc: Li, Fei; Miklos Szeredi; Goswin von Brederlow; Brown, Len; mi...@redhat.com; pet...@infradead.org; Wang, Biao; linux...@vger.kernel.org; fuse-de

RE: Getting rid of freezer for suspend [was Re: [fuse-devel] [PATCH] fuse: make fuse daemon frozen along with kernel threads]

> -Original Message- > From: Rafael J. Wysocki [mailto:r...@sisk.pl] > Sent: Friday, February 15, 2013 1:38 AM > To: Miklos Szeredi > Cc: Pavel Machek; Goswin von Brederlow; Li, Fei; Brown, Len; > mi...@redhat.com; pet...@infradead.org; Wang, Biao; > linux...@vge

RE: Getting rid of freezer for suspend [was Re: [fuse-devel] [PATCH] fuse: make fuse daemon frozen along with kernel threads]

-Original Message- From: Rafael J. Wysocki [mailto:r...@sisk.pl] Sent: Friday, February 15, 2013 1:38 AM To: Miklos Szeredi Cc: Pavel Machek; Goswin von Brederlow; Li, Fei; Brown, Len; mi...@redhat.com; pet...@infradead.org; Wang, Biao; linux...@vger.kernel.org; fuse-de

[PATCH] fuse: make fuse daemon frozen along with kernel threads

, and it's safe to continue to freeze fuse daemon together with kernel freezable tasks. Signed-off-by: Wang Biao Signed-off-by: Liu Chuansheng Signed-off-by: Li Fei --- fs/fuse/inode.c |9 + include/linux/freezer.h |4 include/linux/sched.h |2 ++ kernel

[PATCH] fuse: make fuse daemon frozen along with kernel threads

, and it's safe to continue to freeze fuse daemon together with kernel freezable tasks. Signed-off-by: Wang Biao biao.w...@intel.com Signed-off-by: Liu Chuansheng chuansheng@intel.com Signed-off-by: Li Fei fei...@intel.com --- fs/fuse/inode.c |9 + include/linux/freezer.h

RE: [PATCH V4] suspend: enable freeze timeout configuration through sys

tential issue more quickly with more chance. Taking diversity of system into consideration, we think it's suitable to expose the interface to support different configuration on different system for purpose of debugging and performance tuning. Do you think it make sense for you? Best Regards, L

RE: [PATCH V4] suspend: enable freeze timeout configuration through sys

think it's suitable to expose the interface to support different configuration on different system for purpose of debugging and performance tuning. Do you think it make sense for you? Best Regards, Li Fei And if there is no new wakeup event registered, the system will waste at most 20s

RE: [PATCH V3] suspend: enable freeze timeout configuration through sys

> -Original Message- > From: Rafael J. Wysocki [mailto:r...@sisk.pl] > Sent: Friday, February 01, 2013 6:29 AM > To: anish singh; Li, Fei > Cc: Yasuaki Ishimatsu; a...@linux-foundation.org; > linux-kernel@vger.kernel.org; > linux...@vger.kernel.org; Liu, Chuansheng

RE: [PATCH V3] suspend: enable freeze timeout configuration through sys

> -Original Message- > From: Yasuaki Ishimatsu [mailto:isimatu.yasu...@jp.fujitsu.com] > Sent: Thursday, January 31, 2013 3:30 PM > To: Li, Fei > Cc: r...@sisk.pl; a...@linux-foundation.org; linux-kernel@vger.kernel.org; > linux...@vger.kernel.org; Liu, Chuansheng > S

RE: [PATCH V3] suspend: enable freeze timeout configuration through sys

-Original Message- From: Yasuaki Ishimatsu [mailto:isimatu.yasu...@jp.fujitsu.com] Sent: Thursday, January 31, 2013 3:30 PM To: Li, Fei Cc: r...@sisk.pl; a...@linux-foundation.org; linux-kernel@vger.kernel.org; linux...@vger.kernel.org; Liu, Chuansheng Subject: Re: [PATCH V3

RE: [PATCH V3] suspend: enable freeze timeout configuration through sys

-Original Message- From: Rafael J. Wysocki [mailto:r...@sisk.pl] Sent: Friday, February 01, 2013 6:29 AM To: anish singh; Li, Fei Cc: Yasuaki Ishimatsu; a...@linux-foundation.org; linux-kernel@vger.kernel.org; linux...@vger.kernel.org; Liu, Chuansheng Subject: Re: [PATCH V3

RE: [PATCH V2] suspend: enable freeze timeout configuration through sys

triggered in earlier time. And more power will be saved. In normal case on mobile phone, it costs real little time to freeze processes. On some platform, it only costs about 20ms to freeze user space processes and 10ms to freeze kernel freezable threads. Thanks a lot! Best Regards, Li Fei TEL

RE: [PATCH V2] suspend: enable freeze timeout configuration through sys

triggered in earlier time. And more power will be saved. In normal case on mobile phone, it costs real little time to freeze processes. On some platform, it only costs about 20ms to freeze user space processes and 10ms to freeze kernel freezable threads. Thanks a lot! Best Regards, Li Fei TEL

RE: [PATCH] suspend: enable freeze timeout configuration through sysctl

llisecond will be used for the attribute. Best Regards, Li Fei -Original Message- From: Andrew Morton [mailto:a...@linux-foundation.org] Sent: Wednesday, January 30, 2013 8:37 AM To: Li, Fei Cc: r...@sisk.pl; linux-kernel@vger.kernel.org; linux...@vger.kernel.org; Liu, Chuansheng Subject: R

RE: [PATCH] suspend: enable freeze timeout configuration through sysctl

Hello Rafael, Thanks for your feedback, and my understanding is interleaved in your email as below. Best Regards, Li Fei > -Original Message- > From: Rafael J. Wysocki [mailto:r...@sisk.pl] > Sent: Tuesday, January 29, 2013 7:42 PM > To: Li, Fei > Cc: a...@linux-founda

RE: [PATCH] suspend: enable freeze timeout configuration through sysctl

Hello Rafael, Thanks for your feedback, and my understanding is interleaved in your email as below. Best Regards, Li Fei -Original Message- From: Rafael J. Wysocki [mailto:r...@sisk.pl] Sent: Tuesday, January 29, 2013 7:42 PM To: Li, Fei Cc: a...@linux-foundation.org; linux

RE: [PATCH] suspend: enable freeze timeout configuration through sysctl

will be used for the attribute. Best Regards, Li Fei -Original Message- From: Andrew Morton [mailto:a...@linux-foundation.org] Sent: Wednesday, January 30, 2013 8:37 AM To: Li, Fei Cc: r...@sisk.pl; linux-kernel@vger.kernel.org; linux...@vger.kernel.org; Liu, Chuansheng Subject: Re: [PATCH