From: Dave Olson ol...@cumulusnetworks.com
Fix missing L2 cache in /sys/devices/system/cpu/cpu0/cache/index2/size
This appears to have been introduced in 2.6.29 by
93197a36a9c16a85fb24cf5a8639f7bf9af838a3.
This caused lscpu to error out on e500v2 devices, and probably others
error: cannot open
Sorry for this email . but im facing this error
when try to build the kernel 3.19
ld: unrecognised emulation mode: -T
before with 3.19rc7 everything was build right without issues .
Im using the Ubuntu Mate 14.04 on Quad G5
Gcc 4.8.2
Thanks and sorry
Luigi Burdo
Hi Linus,
Please pull powerpc updates for 3.20:
The following changes since commit b7392d2247cfe6771f95d256374f1a8e6a6f48d6:
Linux 3.19-rc2 (2014-12-28 16:49:37 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mpe/linux.git
tags/powerpc-3.20-1
On 02/11/2015 10:32 AM, Stewart Smith wrote:
Vipin K Parashar vi...@linux.vnet.ibm.com writes:
(1) Environmental and Power Warning (EPOW)
(2) Delayed Power Off (DPO)
The user interface for this driver is /dev/opal_event character
device file where the user space clients can
On Wed, 2015-02-11 at 08:53 +0100, leroy christophe wrote:
In powerpc32 architecture there is a function called cacheable_memcpy()
which does same thing as memcpy() but using dcbz/dcbt instructions for
an optimised copy (just like __copy_tofrom_user())
What seems strange is that it is almost
Signed-off-by: Bogdan Purcareata bogdan.purcare...@freescale.com
---
arch/powerpc/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/powerpc/Kconfig b/arch/powerpc/Kconfig
index a2a168e..72f363e 100644
--- a/arch/powerpc/Kconfig
+++ b/arch/powerpc/Kconfig
@@ -104,6 +104,7 @@ config
The secure_computing_strict will just force the kernel to panic on
secure_computing failure. Once SECCOMP_FILTER support is enabled in the kernel,
syscalls can be denied without system failure.
Signed-off-by: Bogdan Purcareata bogdan.purcare...@freescale.com
---
arch/powerpc/kernel/ptrace.c | 4
On 11.02.2015 05:04, Michael Ellerman wrote:
On Mon, 2015-02-09 at 07:55 +, Bogdan Purcareata wrote:
In certain scenarios - e.g. seccomp filtering with ERRNO as default action -
the system call fails for other reasons than the syscall not being available.
The seccomp filter can be
Add the missing pieces in order to enable SECCOMP_FILTER on PowerPC
architectures, and enable this support.
Testing has been pursued using libseccomp with the latest ppc support patches
[1], on Freescale platforms for both ppc and ppc64. ppc64le support is
untested.
[1]
In certain scenarios - e.g. seccomp filtering with ERRNO as default action -
the system call fails for other reasons than the syscall not being available.
The seccomp filter can be configured to store a user-defined error code on
return from a blacklisted syscall. Don't always set ENOSYS on
On 02/11/2015 11:57 AM, Neelesh Gupta wrote:
Provide an unregister interface for the opal message notifiers
to be called when not needed like during driver unload/remove.
Why only for unload/remove, you can also use it in cases where you need
to abort because of any other error soon after
On 02/11/2015 11:57 AM, Neelesh Gupta wrote:
Fixes the condition check of incoming message type which can
otherwise shoot beyond the message notifiers head array.
Signed-off-by: Neelesh Gupta neele...@linux.vnet.ibm.com
Reviewed-by: Vasant Hegde hegdevas...@linux.vnet.ibm.com
Reviewed-by:
Vipin K Parashar vi...@linux.vnet.ibm.com writes:
- What do UPSs do? It would seem that some common this is what's about
to happen to your power would almost *have* to exist somewhat
generically?
UPS class tells about UPS status with system. FSP sends mbox messages
with UPS status
Correct use of REGISTER/UNREGISTER is to check if the token exists
before calling. If we don't we get a OPAL: Called with bad token 101 !
error, which is harmless but may be alarming to some.
Signed-off-by: Stewart Smith stew...@linux.vnet.ibm.com
---
arch/powerpc/platforms/powernv/opal.c |6
On Wed, 2015-02-11 at 08:36 +, Bogdan Purcareata wrote:
In certain scenarios - e.g. seccomp filtering with ERRNO as default action -
the system call fails for other reasons than the syscall not being available.
The seccomp filter can be configured to store a user-defined error code on
If OPAL firmware is called with an invalid token, that is, one that
the current running firmware does not support, it dumps an error into
its log. For three calls we were making in Linux, we were not adequately
checking that the current firmware supported them, so could get
this warning
Otherwise firmware complains: OPAL: Called with bad token 74 !
as not all OPAL systems have the ability to resend error logs.
Signed-off-by: Stewart Smith stew...@linux.vnet.ibm.com
---
arch/powerpc/platforms/powernv/opal-elog.c |3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff
Not all OPAL platforms support resending system dumps, so check
that current firmware supports it first. Otherwise we get firmware
complaining:
OPAL: Called with bad token 91 !
Signed-off-by: Stewart Smith stew...@linux.vnet.ibm.com
---
arch/powerpc/platforms/powernv/opal-dump.c |3 ++-
1
18 matches
Mail list logo
