"Aneesh Kumar K.V" writes:
> Now that we don't track 4k subpage information we can use 2K PTE
> fragments.
>
> Signed-off-by: Aneesh Kumar K.V
> ---
> arch/powerpc/include/asm/book3s/64/hash-64k.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/arch/powerpc/includ
Russell Currey writes:
> On Fri, 2015-11-27 at 16:40 +1100, Stewart Smith wrote:
>> Russell Currey writes:
>> > On BMC machines, console output is controlled by the OPAL firmware and is
>> > only flushed when its pollers are called. When the kernel is in a panic
>> > state, it no longer calls th
Hi Stewart,
[auto build test ERROR on powerpc/next]
[also build test ERROR on v4.4-rc2 next-20151127]
url:
https://github.com/0day-ci/linux/commits/Stewart-Smith/powerpc-powernv-panic-on-OPAL-V3/20151127-125146
base: https://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git next
con
On 11/23/2015 03:52 PM, Aneesh Kumar K.V wrote:
> Currently we use 4 bits for each slot and pack all the 16 slot
> information related to a 64K linux page in a 64bit value. To do this
> we use 16 bits of pte_t. Move the hash slot valid bit out of pte_t
Looking into the existing function __real_pte
On BMC machines, console output is controlled by the OPAL firmware and is
only flushed when its pollers are called. When the kernel is in a panic
state, it no longer calls these pollers and thus console output does not
completely flush, causing some output from the panic to be lost.
Output is onl
On Fri, 2015-11-27 at 16:40 +1100, Stewart Smith wrote:
> Russell Currey writes:
> > On BMC machines, console output is controlled by the OPAL firmware and is
> > only flushed when its pollers are called. When the kernel is in a panic
> > state, it no longer calls these pollers and thus console o
On 27/11/15 16:43, Stewart Smith wrote:
Considering you need kernel support for any new POWER processor, and we're not
about to do an OPALv4 on POWER8 or earlier - we're going to be safe :)
Not a huge problem then :)
--
Andrew Donnellan Software Engineer, OzLabs
andrew.donnel...@
On 27/11/15 15:45, Stewart Smith wrote:
There was already a check for OPALv3, so we just remove the if/else
check and go for it.
OPAL pre-v3 no longer exists. Anywhere.
Signed-off-by: Stewart Smith
Nothing obviously wrong that stood out to me.
Reviewed-by: Andrew Donnellan
--
Andrew Donn
On 27/11/15 15:45, Stewart Smith wrote:
Long ago, only in the lab, there was OPALv1 and OPALv2. Now there is
just OPALv3, with nobody ever expecting anything on pre-OPALv3 to
be cared about or supported by mainline kernels.
So, let's remove FW_FEATURE_OPAL and instead use FW_FEATURE_OPALv3
exclu
Andrew Donnellan writes:
>> --- a/arch/powerpc/platforms/powernv/opal.c
>> +++ b/arch/powerpc/platforms/powernv/opal.c
>> @@ -103,11 +103,8 @@ int __init early_init_dt_scan_opal(unsigned long node,
>> powerpc_firmware_features |= FW_FEATURE_OPALv2;
>> powerpc_firmware_fea
On 27/11/15 15:45, Stewart Smith wrote:
OPALv2 only ever existed in the lab and didn't escape to the world.
All OPAL systems in the wild are OPALv3.
The probability of there being an OPALv2 system still powered on
anywhere inside IBM is approximately zero, let alone anyone
expecting to run mainl
Russell Currey writes:
> On BMC machines, console output is controlled by the OPAL firmware and is
> only flushed when its pollers are called. When the kernel is in a panic
> state, it no longer calls these pollers and thus console output does not
> completely flush, causing some output from the
On 27/11/15 15:45, Stewart Smith wrote:
The OpenPower Abstraction Layer firmware went through a couple
of iterations in the lab before being released. What we now know
as OPAL advertises itself as OPALv3.
OPALv2 and OPALv1 never made it outside the lab, and the possibility
of anyone at all ever
On 25/11/15 14:26, Russell Currey wrote:
On BMC machines, console output is controlled by the OPAL firmware and is
only flushed when its pollers are called. When the kernel is in a panic
state, it no longer calls these pollers and thus console output does not
completely flush, causing some outpu
Everything that ever made it out of the lab is OPALv3.
The number of machines in the lab even that are OPAL pre v3 is so
likely to be zero it's not funny, and the number of people expecting
to run mainline kernels on OPAL pre v3 is even lower than that.
So, this patch series removes things refere
The OpenPower Abstraction Layer firmware went through a couple
of iterations in the lab before being released. What we now know
as OPAL advertises itself as OPALv3.
OPALv2 and OPALv1 never made it outside the lab, and the possibility
of anyone at all ever building a mainline kernel today and expec
There was already a check for OPALv3, so we just remove the if/else
check and go for it.
OPAL pre-v3 no longer exists. Anywhere.
Signed-off-by: Stewart Smith
---
arch/powerpc/platforms/powernv/smp.c | 68 +++-
1 file changed, 29 insertions(+), 39 deletions(-)
di
Long ago, only in the lab, there was OPALv1 and OPALv2. Now there is
just OPALv3, with nobody ever expecting anything on pre-OPALv3 to
be cared about or supported by mainline kernels.
So, let's remove FW_FEATURE_OPAL and instead use FW_FEATURE_OPALv3
exclusively.
Signed-off-by: Stewart Smith
---
OPALv2 only ever existed in the lab and didn't escape to the world.
All OPAL systems in the wild are OPALv3.
The probability of there being an OPALv2 system still powered on
anywhere inside IBM is approximately zero, let alone anyone
expecting to run mainline kernels.
So, start to remove referenc
This is a *very* RFC patch and one that is no doubt missing something
fairly important that I don't even know about (along with the things
that I know it's lacking).
i.e. don't merge this.
However, posting for discussion of the possibility of enabling winkle
as a cpuidle state on powernv as curre
On 11/26/15, Michael Ellerman wrote:
> On Thu, 2015-11-26 at 11:15 +0300, Denis Kirjanov wrote:
>> On 11/26/15, Michael Ellerman wrote:
>> > On Tue, 2015-11-24 at 21:23 +0300, Denis Kirjanov wrote:
>> > I can't get this to hit.
>> >
>> > I've got LOCKDEP=y, I've enabled the hcall tracepoints, and
On 11/23/2015 03:52 PM, Aneesh Kumar K.V wrote:
> Only difference here is, we apply the WIMG mapping early, so rflags
> passed to updatepp will also be changed.
This patch can be folded back with the previous patch.
___
Linuxppc-dev mailing list
Linuxpp
On 11/23/2015 03:52 PM, Aneesh Kumar K.V wrote:
> We should not expect pte bit position in asm code. Simply
> by moving part of that to C
There is a full stop missing in the second sentence. The commit
message here does not tell about why we would want to process the
page access flags or other PTE
On Thu, Nov 26, 2015 at 01:04:19PM +0300, Denis Kirjanov wrote:
> On 11/25/15, Torsten Duwe wrote:
> > --- a/arch/powerpc/kernel/entry_64.S
> > +++ b/arch/powerpc/kernel/entry_64.S
> Linux style for comments is the C89. Please update entry_64.S
I might as well switch to asm-style comments. Anyway
On Thu, Nov 26, 2015 at 01:12:12PM +0300, Denis Kirjanov wrote:
> On 11/25/15, Torsten Duwe wrote:
> > +*/
> > + return 2;
> I didn't find where you check for this return value.
That's a pure debugging convenience. The return test is for != 0,
so any non-zero
On 26/11/15 13:09, Michael Ellerman wrote:
> On Thu, 2015-11-26 at 11:47 +0100, Thomas Huth wrote:
>
>> On 26/11/15 01:59, Rashmica Gupta wrote:
>
>>> All users of QPACE have upgraded to QPACE2 so remove the Cell QPACE code.
>>>
>>> Signed-off-by: Rashmica Gupta
>>> ---
>>> arch/powerpc/boot/Ma
On Thu, 2015-19-11 at 06:04:53 UTC, Rashmica Gupta wrote:
> Most architectures use NR_syscalls as the #define for the number of syscalls.
>
> We use __NR_syscalls, and then define NR_syscalls as __NR_syscalls.
>
> __NR_syscalls is not used outside arch code, whereas NR_syscalls is. So as
> NR_sys
On Wed, 2015-11-11 at 13:48:50 UTC, John Ogness wrote:
> The xmon and cascade irq handlers must not run as threads.
> pmac_pic_lock is already a raw_spinlock, but the irq flag
> IRQF_NO_THREAD needs to be set as well.
>
> Signed-off-by: John Ogness
Applied to powerpc next, thanks.
https://git.k
On Thu, 2015-19-11 at 03:26:28 UTC, Rashmica Gupta wrote:
> This function has been unused since commit 14cf11af6cf6 ("powerpc: Merge
> enough
> to start building in arch/powerpc."), so remove it.
>
> Signed-off-by: Rashmica Gupta
> Reviewed-by: Andrew Donnellan
> Reviewed-by: Anshuman Khandual
On Tue, 2015-20-10 at 15:13:53 UTC, Luis de Bethencourt wrote:
> From: Luis de Bethencourt
>
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
Applied to powerpc next, th
On Wed, 2015-11-11 at 14:15:03 UTC, John Ogness wrote:
> Since gpio1 is not a timer, it also should not use IRQF_TIMER.
>
> Similar to commit ba461f094bab ("powerpc: Use IRQF_NO_SUSPEND not
> IRQF_TIMER for non-timer interrupts").
>
> Signed-off-by: John Ogness
Applied to powerpc next, thanks.
On Sat, 2015-21-11 at 06:08:16 UTC, Rashmica Gupta wrote:
> It is common practice with powerpc to use 'rN' to refer to register 'N'.
> However
> when using the pt_regs_offset table we have to use 'gprN'.
>
> So add aliases such that both 'rN' and 'gprN' can be used.
>
> For example, we can curre
On Thu, 2015-19-11 at 04:00:39 UTC, Krzysztof Kozlowski wrote:
> platform_driver does not need to set an owner because
> platform_driver_register() will set it.
>
> Signed-off-by: Krzysztof Kozlowski
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/87630eb1d5ab76fc39e78529
che
On Wed, 2015-04-11 at 02:24:09 UTC, Andrew Donnellan wrote:
> When writing a value to config space, cxl_pcie_write_config() calls
> cxl_pcie_config_info() to obtain a mask and shift value, shifts the new
> value accordingly, then uses the mask to combine the shifted value with the
> existing value
On Mon, 2015-16-11 at 04:03:45 UTC, Vaibhav Jain wrote:
> An idr warning is reported when a context is release after the capi card
> is unbound from the cxl driver via sysfs. Below are the steps to
> reproduce:
>
> 1. Create multiple afu contexts in an user-space application using libcxl.
> 2. Unb
On Thu, 2015-05-11 at 11:31:34 UTC, Laurent Vivier wrote:
> if the language is not english objdump output is not parsed correctly
> and format is "". Later, "ld -m $format" fails.
>
> This patch adds "LANG=C" to force english output for objdump.
>
> Signed-off-by: Laurent Vivier
Applied to powe
On Tue, 2015-20-10 at 15:04:13 UTC, Luis de Bethencourt wrote:
> From: Luis de Bethencourt
>
> This platform driver has a OF device ID table but the OF module
> alias information is not created so module autoloading won't work.
>
> Signed-off-by: Luis de Bethencourt
Applied to powerpc next, th
On Thu, 2015-19-11 at 04:44:45 UTC, Michael Neuling wrote:
> Currently we can hit a scenario where we'll tm_reclaim() twice. This
> results in a TM bad thing exception because the second reclaim occurs
> when not in suspend mode.
Applied to powerpc fixes, thanks.
https://git.kernel.org/powerpc/c
On Thu, 2015-19-11 at 04:44:44 UTC, Michael Neuling wrote:
> Currently we allow both the MSR T and S bits to be set by userspace on
> a signal return. Unfortunately this is a reserved configuration and
> will cause a TM Bad Thing exception if attempted (via rfid).
Applied to powerpc fixes, thanks
Hi Linus,
Please pull some more powerpc fixes for 4.4:
The following changes since commit 1ec218373b8ebda821aec00bb156a9c94fad9cd4:
Linux 4.4-rc2 (2015-11-22 16:45:59 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux.git
tags/powerp
On Thu, 2015-11-26 at 11:47 +0100, Thomas Huth wrote:
> On 26/11/15 01:59, Rashmica Gupta wrote:
> > All users of QPACE have upgraded to QPACE2 so remove the Cell QPACE code.
> >
> > Signed-off-by: Rashmica Gupta
> > ---
> > arch/powerpc/boot/Makefile| 2 -
> > arch/powerpc/c
On 26/11/15 01:59, Rashmica Gupta wrote:
> All users of QPACE have upgraded to QPACE2 so remove the Cell QPACE code.
>
> Signed-off-by: Rashmica Gupta
> ---
> arch/powerpc/boot/Makefile| 2 -
> arch/powerpc/configs/ppc64_defconfig | 1 -
> arch/powerpc/platforms/cell/Kco
On 11/25/15, Torsten Duwe wrote:
> The gcc switch -mprofile-kernel, available for ppc64 on gcc > 4.8.5,
> allows to call _mcount very early in the function, which low-level
> ASM code and code patching functions need to consider.
> Especially the link register and the parameter registers are still
On 11/25/15, Torsten Duwe wrote:
> Implement FTRACE_WITH_REGS for powerpc64, on ELF ABI v2.
> Initial work started by Vojtech Pavlik, used with permission.
>
> * arch/powerpc/kernel/entry_64.S:
> - Implement an effective ftrace_caller that works from
> within the kernel binary as well
Thanks.
I just sent the new patch.
> -Original Message-
> From: Viresh Kumar [mailto:viresh.ku...@linaro.org]
> Sent: Thursday, November 26, 2015 5:08 PM
> To: Jia Hongtao-B38951
> Cc: edubez...@gmail.com; linux...@vger.kernel.org; linuxppc-
> d...@lists.ozlabs.org; devicet...@vger.kernel.
Register the qoriq cpufreq driver as a cooling device, based on the
thermal device tree framework. When temperature crosses the passive trip
point cpufreq is used to throttle CPUs.
Signed-off-by: Jia Hongtao
Reviewed-by: Viresh Kumar
---
Changes for V3:
* Removed unnecessary cpu node NULL check.
On Thu, 2015-11-26 at 11:15 +0300, Denis Kirjanov wrote:
> On 11/26/15, Michael Ellerman wrote:
> > On Tue, 2015-11-24 at 21:23 +0300, Denis Kirjanov wrote:
> > I can't get this to hit.
> >
> > I've got LOCKDEP=y, I've enabled the hcall tracepoints, and then I offline
> > a cpu via sysfs.
> I ha
On 11/18/2015 02:12 PM, Vipin K Parashar wrote:
> Kernel prints respective warnings about various EPOW events for
> user information/action after parsing EPOW interrupts. At times
> below EPOW reset event warning is seen to be flooding kernel log
> over a period of time.
>
> May 25 03:46:34 alp ke
On 26-11-15, 14:27, Jia Hongtao wrote:
> +static void qoriq_cpufreq_ready(struct cpufreq_policy *policy)
> +{
> + struct cpu_data *cpud = policy->driver_data;
> + struct device_node *np = of_get_cpu_node(policy->cpu, NULL);
> +
> + if (WARN_ON(!np))
> + return;
Drop this an
> -Original Message-
> From: Denis Kirjanov [mailto:k...@linux-powerpc.org]
> Sent: Thursday, November 26, 2015 4:32 PM
> To: Jia Hongtao-B38951
> Cc: edubez...@gmail.com; viresh.ku...@linaro.org; Wood Scott-B07421;
> devicet...@vger.kernel.org; linuxppc-dev@lists.ozlabs.org; linux-
> p..
On 11/26/15, Jia Hongtao wrote:
> Register the qoriq cpufreq driver as a cooling device, based on the
> thermal device tree framework. When temperature crosses the passive trip
> point cpufreq is used to throttle CPUs.
>
> Signed-off-by: Jia Hongtao
> ---
> Changes for V2:
> * Using ->ready callb
On 11/26/15, Michael Ellerman wrote:
> On Tue, 2015-11-24 at 21:23 +0300, Denis Kirjanov wrote:
>
>> ./drmgr -c cpu -a -r gives the following warning:
>>
>> [ 2327.035563] RCU used illegally from offline CPU!
>> rcu_scheduler_active = 1, debug_locks = 1
>> [ 2327.035564] no locks held by swapper/1
52 matches
Mail list logo
