From: Liu ShuoX
In ramoops_pstore_read, a valid prz pointer with zero size buffer will
break traverse of all persistent ram buffers. The latter buffer might
be lost.
Signed-off-by: Liu ShuoX
---
fs/pstore/ram.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
From: Liu ShuoX
ftrace_read_cnt need to be reset in open to support mutli times
getting the records.
Signed-off-by: Liu ShuoX
---
fs/pstore/ram.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index fa8cef2..a5d0cab 100644
--- a/fs/pstore/ram.c
+++
From: Liu ShuoX shuox@intel.com
In ramoops_pstore_read, a valid prz pointer with zero size buffer will
break traverse of all persistent ram buffers. The latter buffer might
be lost.
Signed-off-by: Liu ShuoX shuox@intel.com
---
fs/pstore/ram.c | 10 +-
1 file changed, 5
From: Liu ShuoX shuox@intel.com
ftrace_read_cnt need to be reset in open to support mutli times
getting the records.
Signed-off-by: Liu ShuoX shuox@intel.com
---
fs/pstore/ram.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/fs/pstore/ram.c b/fs/pstore/ram.c
index fa8cef2..a5d0cab
From: Zhang Yanmin
pnp pnp_bus_suspend/_resume have an issue.
pnp_bus_suspend calls pnp_stop_dev to disable the device. With ACPI,
pnp_stop_dev turns off the dev usually. Then,
pnp_bus_suspend=>pnp_dev->protocol->suspend accesses the device and
suspend it again.
pnp_bus_resume has the similar
From: Zhang Yanmin yanmin.zh...@intel.com
pnp pnp_bus_suspend/_resume have an issue.
pnp_bus_suspend calls pnp_stop_dev to disable the device. With ACPI,
pnp_stop_dev turns off the dev usually. Then,
pnp_bus_suspend=pnp_dev-protocol-suspend accesses the device and
suspend it again.
From: Liu ShuoX
Set temporary variable as 0 to avoid garbage string output from
/proc/iomem after register resources, and reset to pnp dev name.
Signed-off-by: Liu ShuoX
---
drivers/pnp/pnpacpi/rsparser.c | 2 +-
drivers/pnp/resource.c | 1 +
2 files changed, 2 insertions(+), 1
From: Liu ShuoX shuox@intel.com
Set temporary variable as 0 to avoid garbage string output from
/proc/iomem after register resources, and reset to pnp dev name.
Signed-off-by: Liu ShuoX shuox@intel.com
---
drivers/pnp/pnpacpi/rsparser.c | 2 +-
drivers/pnp/resource.c | 1 +
2
From: Liu ShuoX
In shutdown progress, system is possible to do power transition
(such as suspend-to-ram) in parallel. It is unreasonable. So,
fixes it by adding a system_state checking and queue try_to_suspend
again when system status is not running.
Signed-off-by: Liu ShuoX
---
From: Liu ShuoX shuox@intel.com
In shutdown progress, system is possible to do power transition
(such as suspend-to-ram) in parallel. It is unreasonable. So,
fixes it by adding a system_state checking and queue try_to_suspend
again when system status is not running.
Signed-off-by: Liu ShuoX
On 2013-06-08 18:54, Rafael J. Wysocki wrote:
> On Saturday, June 08, 2013 10:37:18 AM Yanmin Zhang wrote:
>> On Sat, 2013-06-08 at 03:52 +0200, Rafael J. Wysocki wrote:
>>> On Saturday, June 08, 2013 09:36:03 AM Yanmin Zhang wrote:
On Sat, 2013-06-08 at 03:30 +0200, Rafael J. Wysocki wrote:
On 2013-06-08 18:54, Rafael J. Wysocki wrote:
On Saturday, June 08, 2013 10:37:18 AM Yanmin Zhang wrote:
On Sat, 2013-06-08 at 03:52 +0200, Rafael J. Wysocki wrote:
On Saturday, June 08, 2013 09:36:03 AM Yanmin Zhang wrote:
On Sat, 2013-06-08 at 03:30 +0200, Rafael J. Wysocki wrote:
On
From: ShuoX Liu
dpm_run_callback_void could show more debug info around complete stage
Signed-off-by: Zhang Yanmin
Signed-off-by: Liu ShuoX
---
drivers/base/power/main.c | 27 ++-
1 files changed, 22 insertions(+), 5 deletions(-)
diff --git a/drivers/base/power
dpm_run_callback is used in other stages of power states changing.
It provides debug info message and time measurement when call these
callback. We also want to benefit ->prepare and ->complete.
[PATCH 1/2] PM: use dpm_run_callback in device_prepare
[PATCH 2/2] PM: add dpm_run_callback_void and
From: ShuoX Liu
dpm_run_callback could show more debug info around prepare stage.
Signed-off-by: Zhang Yanmin
Signed-off-by: Liu ShuoX
---
drivers/base/power/main.c |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/drivers/base/power/main.c b/drivers/base/power
From: ShuoX Liu shuox@intel.com
dpm_run_callback could show more debug info around prepare stage.
Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com
Signed-off-by: Liu ShuoX shuox@intel.com
---
drivers/base/power/main.c |9 -
1 files changed, 4 insertions(+), 5 deletions
dpm_run_callback is used in other stages of power states changing.
It provides debug info message and time measurement when call these
callback. We also want to benefit -prepare and -complete.
[PATCH 1/2] PM: use dpm_run_callback in device_prepare
[PATCH 2/2] PM: add dpm_run_callback_void and use
From: ShuoX Liu shuox@intel.com
dpm_run_callback_void could show more debug info around complete stage
Signed-off-by: Zhang Yanmin yanmin.zh...@intel.com
Signed-off-by: Liu ShuoX shuox@intel.com
---
drivers/base/power/main.c | 27 ++-
1 files changed, 22
From: Zhang Yanmin
synchronize_irq waits pending IRQ handlers to be finished. If using this
function while holding a resource, the IRQ handler may cause deadlock.
Here we add a new function irq_in_progress which doesn't wait for the handlers
to be finished.
A typical use case at
From: Zhang Yanmin yanmin.zh...@intel.com
synchronize_irq waits pending IRQ handlers to be finished. If using this
function while holding a resource, the IRQ handler may cause deadlock.
Here we add a new function irq_in_progress which doesn't wait for the handlers
to be finished.
A typical use
Commit-ID: 0927b482ae69acb7605f6be1ad3860b657512fbd
Gitweb: http://git.kernel.org/tip/0927b482ae69acb7605f6be1ad3860b657512fbd
Author: ShuoX Liu
AuthorDate: Sat, 29 Dec 2012 00:48:44 +0800
Committer: Ingo Molnar
CommitDate: Thu, 24 Jan 2013 15:10:03 +0100
perf/x86: Enable Intel
Commit-ID: 0927b482ae69acb7605f6be1ad3860b657512fbd
Gitweb: http://git.kernel.org/tip/0927b482ae69acb7605f6be1ad3860b657512fbd
Author: ShuoX Liu shuox@intel.com
AuthorDate: Sat, 29 Dec 2012 00:48:44 +0800
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Thu, 24 Jan 2013 15:10:03
From: ShuoX Liu
This boolean function simply returns whether or not the runtime
status of the device is 'active'. The typical scenario is driver
calls pm_runtime_get firstly, then check pm_runtime_active in
atomic environment.
Also add entry to Documentation/power/runtime.txt
Signed-off
From: ShuoX Liu shuox@intel.com
This boolean function simply returns whether or not the runtime
status of the device is 'active'. The typical scenario is driver
calls pm_runtime_get firstly, then check pm_runtime_active in
atomic environment.
Also add entry to Documentation/power/runtime.txt
From: ShuoX Liu
These three chip are based on Atom and have different model id.
So add such three id for perf HW event support.
Signed-off-by: ShuoX Liu
---
arch/x86/kernel/cpu/perf_event_intel.c |3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kernel/cpu
From: ShuoX Liu shuox@intel.com
These three chip are based on Atom and have different model id.
So add such three id for perf HW event support.
Signed-off-by: ShuoX Liu shuox@intel.com
---
arch/x86/kernel/cpu/perf_event_intel.c |3 +++
1 files changed, 3 insertions(+), 0 deletions
From: ShuoX Liu
syscore_shutdown uses initcall_debug to control the debug info output.
It’s a good programming. But device_shutdown doesn’t. The patch changes
device_shutdown to follow the style.
Signed-off-by: Yanmin Zhang
Signed-off-by: ShuoX Liu
---
drivers/base/core.c |6 --
1
From: ShuoX Liu shuox@intel.com
syscore_shutdown uses initcall_debug to control the debug info output.
It’s a good programming. But device_shutdown doesn’t. The patch changes
device_shutdown to follow the style.
Signed-off-by: Yanmin Zhang yanmin_zh...@linux.intel.com
Signed-off-by: ShuoX
28 matches
Mail list logo
