On 01/14/2014 12:30 PM, Srivatsa S. Bhat wrote:
> On 01/14/2014 11:35 AM, Preeti U Murthy wrote:
>> On PowerPC, in a particular test scenario, all the cpu idle states were
>> disabled.
>> Inspite of this it was observed that the idle state count of the shallowest
>> idle state, snooze, was increas
From: Wang Dongsheng
E500MC and E5500 PVR will be used in subsequent save/restore core
state patches.
Signed-off-by: Wang Dongsheng
diff --git a/arch/powerpc/include/asm/reg.h b/arch/powerpc/include/asm/reg.h
index 62b114e..cd7b630 100644
--- a/arch/powerpc/include/asm/reg.h
+++ b/arch/powerpc
From: Wang Dongsheng
Use fsl_cpu_state_save/fsl_cpu_state_restore to save/restore registers.
Use the functions to save/restore registers, so we don't need to
maintain the code.
Signed-off-by: Wang Dongsheng
diff --git a/arch/powerpc/kernel/swsusp_booke.S
b/arch/powerpc/kernel/swsusp_booke.S
i
From: Wang Dongsheng
Add fsl_cpu_state_save/fsl_cpu_state_restore functions, used for deep
sleep and hibernation to save/restore core registers. We abstract out
save/restore code for use in various modules, to make them don't need
to maintain.
Currently supported processors type are E6500, E5500
On Mon, 2014-01-13 at 23:47 -0800, Hugh Dickins wrote:
>
> And I may be quite wrong to point a finger at ATA errors: perhaps
> they're always shown, and quickly cleared off screen in successful
> boots,
> but left visible when root cannot be mounted for some other reason.
dmesg would tell...
> I
Hi Srivatsa,
On 01/14/2014 12:30 PM, Srivatsa S. Bhat wrote:
> On 01/14/2014 11:35 AM, Preeti U Murthy wrote:
>> On PowerPC, in a particular test scenario, all the cpu idle states were
>> disabled.
>> Inspite of this it was observed that the idle state count of the shallowest
>> idle state, snooz
Hi Christophe,
> Convert mpc8xxx_wdt.c to the new watchdog API.
>
> Signed-off-by: Christophe Leroy
This patch has been added to linux-watchdog-next.
Kind regards,
Wim.
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs
Without this patch, kind of below error will be dumped if
'insmod ixgbevf.ko' is executed:
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function
Network Driver - version 2.7.12-k
ixgbevf: Copyright (c) 2009 - 2012 Intel Corporation.
ixgbevf :01:10.0: enabling devic
On Tue, 2014-01-14 at 17:44 +0800, Chunhe Lan wrote:
> Without this patch, kind of below error will be dumped if
> 'insmod ixgbevf.ko' is executed:
>
> ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function
> Network Driver - version 2.7.12-k
> ixgbevf: Copyright (c) 2009 -
From: Mahesh Salgaonkar
Huge Dickins reported an issue that b5ff4211a829
"powerpc/book3s: Queue up and process delayed MCE events" breaks the
PowerMac G5 boot. This patch fixes it by moving the mce even processing
away from syscall exit, which was wrong to do that in first place, and
using irq wo
The following patch series includes a bunch of clean-ups for the
pseries cpuidle backend driver. This includes,
moving the driver from arch/powerpc/platforms/pseries to
driver/cpuidle, refactoring of the code, making it a non-module,
removing smt-snooze-delay update and dead code around it.
After
From: Preeti U Murthy
Commit fbd7740fdfdf9475f(powerpc: Simplify pSeries idle loop) switched pseries
cpu idle handling from complete idle loops to ppc_md.powersave functions.
Earlier to this switch, ppc64_runlatch_off() had to be called in each of the
idle routines. But after the switch, this cal
Move the file from arch specific pseries/processor_idle.c
to drivers/cpuidle/cpuidle-pseries.c
Make the relevant Makefile and Kconfig changes.
Also, introduce Kconfig.powerpc in drivers/cpuidle
for all powerpc cpuidle drivers.
Signed-off-by: Deepthi Dharwar
---
arch/powerpc/include/asm/processor
This patch replaces the cpuidle driver and devices initialisation
calls with a single generic cpuidle_register() call
and also includes minor refactoring of the code around it.
Remove the cpu online check in snooze loop, as this code can
only locally run on a cpu only if it is online. Therefore,
t
Currently cpuidle-pseries backend driver cannot be
built as a module due to dependencies wrt cpuidle framework.
This patch removes all the module related code in the driver.
Signed-off-by: Deepthi Dharwar
---
drivers/cpuidle/cpuidle-pseries.c | 15 +--
1 file changed, 1 insertion(+
This patch removes the usage of MAX_IDLE_STATE macro
and dead code around it. The number of states
are determined at run time based on the cpuidle
state table selected on a given platform
Signed-off-by: Deepthi Dharwar
---
drivers/cpuidle/cpuidle-pseries.c | 28 ++--
1
smt-snooze-delay was designed to disable NAP state or delay the entry
to the NAP state prior to adoption of cpuidle framework. This
is per-cpu variable. With the coming of CPUIDLE framework,
states can be disabled on per-cpu basis using the cpuidle/enable
sysfs entry.
Also, with the coming of cpui
Following patch ports the cpuidle framework for powernv
platform and also implements a cpuidle back-end powernv
idle driver calling on to power7_nap and snooze idle states.
Moving the idle states over to cpuidle framework can take advantage
of advanced heuristics, tunables and features provided
Following patch ports the cpuidle framework for powernv
platform and also implements a cpuidle back-end powernv
idle driver calling on to power7_nap and snooze idle states.
Signed-off-by: Deepthi Dharwar
---
arch/powerpc/platforms/powernv/setup.c | 13 ++
drivers/cpuidle/Kconfig.powerpc
On 01/14/2014 01:07 PM, Srivatsa S. Bhat wrote:
> On 01/14/2014 12:30 PM, Srivatsa S. Bhat wrote:
>> On 01/14/2014 11:35 AM, Preeti U Murthy wrote:
>>> On PowerPC, in a particular test scenario, all the cpu idle states were
>>> disabled.
>>> Inspite of this it was observed that the idle state coun
I am looking for info on when and how we are able to disable power saving
features of current (P7, P7+) chips in order to reduce latency. This is often
done in latency sensitive applications when power consumption is not an issue.
On Intel boxes we can disable P-state frequency changes as well a
Hi Steven,
On 01/14/2014 08:06 PM, Steven Pratt wrote:
> I am looking for info on when and how we are able to disable power saving
> features of current (P7, P7+) chips in order to reduce latency. This is often
> done in latency sensitive applications when power consumption is not an
> issue. O
On 01/14/2014 10:10 AM, Preeti U Murthy wrote:
> Hi Steven,
>
> On 01/14/2014 08:06 PM, Steven Pratt wrote:
>> I am looking for info on when and how we are able to disable power saving
>> features of current (P7, P7+) chips in order to reduce latency. This is
>> often done in latency sensitive ap
On Tue, 2014-01-14 at 11:48 -0800, Hugh Dickins wrote:
> On Tue, 14 Jan 2014, Mahesh J Salgaonkar wrote:
> > From: Mahesh Salgaonkar
> >
> > Huge Dickins reported an issue that b5ff4211a829
> > "powerpc/book3s: Queue up and process delayed MCE events" breaks the
> > PowerMac G5 boot. This patch f
On Mon, 2014-01-13 at 11:21 -0500, Paul Gortmaker wrote:
> The FSL_SOC option is bool, and hence this code is either
> present or absent. It will never be modular, so using
> module_init as an alias for __initcall is rather misleading.
>
> Fix this up now, so that we can relocate module_init from
On Tue, 2014-01-14 at 15:59 +0800, Dongsheng Wang wrote:
> From: Wang Dongsheng
>
> Use fsl_cpu_state_save/fsl_cpu_state_restore to save/restore registers.
> Use the functions to save/restore registers, so we don't need to
> maintain the code.
>
> Signed-off-by: Wang Dongsheng
Is there any fun
On Tue, 2014-01-14 at 15:59 +0800, Dongsheng Wang wrote:
> From: Wang Dongsheng
>
> Add fsl_cpu_state_save/fsl_cpu_state_restore functions, used for deep
> sleep and hibernation to save/restore core registers. We abstract out
> save/restore code for use in various modules, to make them don't need
On Wed, Oct 23, 2013 at 05:31:22PM +0800, Tiejun Chen wrote:
> We need to store thread info to these exception thread info like something
> we already did for PPC32.
>
> Signed-off-by: Tiejun Chen
>
> ---
> arch/powerpc/kernel/exceptions-64e.S | 22 +++---
> 1 file changed, 19
> -Original Message-
> From: Wood Scott-B07421
> Sent: Wednesday, January 15, 2014 7:30 AM
> To: Wang Dongsheng-B40534
> Cc: b...@kernel.crashing.org; Zhao Chenhui-B35336; an...@enomsg.org; linuxppc-
> d...@lists.ozlabs.org
> Subject: Re: [PATCH 3/3] powerpc/fsl: Use the new interface to
> -Original Message-
> From: Wood Scott-B07421
> Sent: Wednesday, January 15, 2014 7:51 AM
> To: Wang Dongsheng-B40534
> Cc: b...@kernel.crashing.org; Zhao Chenhui-B35336; an...@enomsg.org; linuxppc-
> d...@lists.ozlabs.org
> Subject: Re: [PATCH 2/3] powerpc/85xx: Provide two functions to
On 01/14/2014 06:14 PM, Benjamin Herrenschmidt wrote:
On Tue, 2014-01-14 at 17:44 +0800, Chunhe Lan wrote:
Without this patch, kind of below error will be dumped if
'insmod ixgbevf.ko' is executed:
ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function
Network Driver - ver
On Wed, 2014-01-15 at 11:36 +0800, Chunhe Lan wrote:
> >
> >> Signed-off-by: Chunhe Lan
> >> Cc: Benjamin Herrenschmidt
> >> Tested-by: Chunhe Lan
> >> ---
> >> arch/powerpc/include/asm/dma-mapping.h | 13 +
> >> 1 files changed, 9 insertions(+), 4 deletions(-)
> >>
> >> diff -
On Fri, 2014-01-10 at 18:44 -0600, Scott Wood wrote:
> Highlights include 32-bit booke relocatable support, e6500 hardware
> tablewalk support, various e500 SPE fixes, some new/revived boards, and
> e6500 deeper idle and altivec powerdown modes.
This breaks WSP (A2) build with 64K pages:
/home/be
Hi Linus !
So you make the call onto whether taking that one now or waiting for the
merge window. It's a bug fix for a crash in mremap that occurs on
powerpc with THP enabled.
The fix however requires a small change in the generic code. It moves a
condition into a helper we can override from the
Sometimes, especially in sinario of loading another kernel with kdump,
we got EEH error on non-existing PE. That means the PEEV / PEST in
the corresponding PHB would be messy and we can't handle that case.
The patch escalates the error to fenced PHB so that the PHB could be
rested in order to revoe
For one PCI error relevant OPAL event, we possibly have multiple
EEH errors for that. For example, multiple frozen PEs detected on
different PHBs. Unfortunately, we didn't cover the case. The patch
enumarates the return value from eeh_ops::next_error() and change
eeh_handle_special_event() and eeh_
When EEH error comes to one specific PCI device before its driver
is loaded, we will apply hotplug to recover the error. During the
plug time, the PCI device will be probed and its driver is loaded.
Then we wrongly calls to the error handlers if the driver supports
EEH explicitly.
The patch intend
From: Vasant Hegde
Its possible that OPAL may be writing to host memory during
kexec (like dump retrieve scenario). In this situation we might
end up corrupting host memory.
This patch makes OPAL sync call to make sure OPAL stops
writing to host memory before kexec'ing.
Signed-off-b
On Thu, Jan 9, 2014 at 8:08 PM, Alexander Graf wrote:
>
> On 11.12.2013, at 09:47, Liu Ping Fan wrote:
>
>> This series is based on Aneesh's series "[PATCH -V2 0/5] powerpc: mm: Numa
>> faults support for ppc64"
>>
>> For this series, I apply the same idea from the previous thread "[PATCH 0/3]
As of now "echo p > /proc/sysrq-trigger" command does not print anything on
the console as we have a blank perf_event_print_debug function. This patch
defines perf_event_print_debug function to print various PMU registers.
With this patch, "echo p > /proc/sysrq-trigger" command on a POWER8 system
This commit adds the architecture support required to enable the
optimised implementation of lockrefs.
That's as simple as defining arch_spin_value_unlocked() and selecting
the Kconfig option.
We also define cmpxchg64_relaxed(), because the lockref code does not
need the cmpxchg to have barrier s
At a glance these are just the inverse of each other. The one subtlety
is that arch_spin_value_unlocked() takes the lock by value, rather than
as a pointer, which is important for the lockref code.
On the other hand arch_spin_is_locked() doesn't really care, so
implement it in terms of arch_spin_v
42 matches
Mail list logo
