On Wed, May 19, 2021 at 11:50:44AM +0200, Emmanuel Gil Peyrot wrote:
> This selects the nintendo-otp module when building for this platform, if
> CONFIG_NVMEM is also selected.
The 'if' is a bit confusing. CONFIG_NVRAM=y has indeed been in
wii_defconfig since 2009.
Thanks,
Jonathan Neuschäfer
On Wed, May 19, 2021 at 11:50:43AM +0200, Emmanuel Gil Peyrot wrote:
> This can be used by the newly-added nintendo-otp nvmem module.
>
> Signed-off-by: Emmanuel Gil Peyrot
> ---
> arch/powerpc/boot/dts/wii.dts | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/arch/powerpc/boot/dts/
Hi,
On Wed, May 19, 2021 at 11:50:41AM +0200, Emmanuel Gil Peyrot wrote:
> This OTP is read-only and contains various keys used by the console to
> decrypt, encrypt or verify various pieces of storage.
>
> Its size depends on the console, it is 128 bytes on the Wii and
> 1024 bytes on the Wii U
Hello and sorry for the delay,
On Wed, May 19, 2021 at 11:50:42AM +0200, Emmanuel Gil Peyrot wrote:
> Both of these consoles use the exact same two registers, even at the
> same address, but the Wii U has eight banks of 128 bytes memory while
> the Wii only has one, hence the two compatible string
randconfig-a015-20210622
x86_64 randconfig-a014-20210622
x86_64 randconfig-a013-20210622
x86_64 randconfig-a011-20210622
i386 randconfig-a011-20210626
i386 randconfig-a014-20210626
i386 randconfig-a013-20210626
riable 'ea' is
uninitialized when used here [-Werror,-Wuninitialized]
Error/Warning ids grouped by kconfigs:
clang_recent_errors
`-- powerpc64-buildonly-randconfig-r006-20210626
`--
arch-powerpc-kernel-hw_breakpoint.c:error:variable-ea-is-uninitialized-when-used-here-Werror-Wuniniti
Excerpts from Sachin Sant's message of June 26, 2021 11:52 pm:
> Following kernel warning is seen while booting 5.13.0-rc7-next-20210625
> on POWER9 LPAR.
>
> [ 40.573592] [ cut here ]
> [ 40.573604] WARNING: CPU: 6 PID: 4743 at
> arch/powerpc/kernel/interrupt.c:518 in
On Thu, Jun 24, 2021 at 1:07 AM Vaibhav Jain wrote:
>
> Persistent memory devices like NVDIMMs can loose cached writes in case
> something prevents flush on power-fail. Such situations are termed as
> dirty shutdown and are exposed to applications as
> last-shutdown-state (LSS) flag and a dirty-sh
Following kernel warning is seen while booting 5.13.0-rc7-next-20210625
on POWER9 LPAR.
[ 40.573592] [ cut here ]
[ 40.573604] WARNING: CPU: 6 PID: 4743 at arch/powerpc/kernel/interrupt.c:518
interrupt_exit_kernel_prepare+0x280/0x2a0
[ 40.573614] Modules linked in: d
On Wed, 19 May 2021 16:17:16 +0530, Naveen N. Rao wrote:
> Various fixes and some code refactoring for kprobes on powerpc. The
> first patch fixes an invalid access if probing the first instruction in
> a kernel module. The rest are small cleanups. More details in the
> individual patches.
>
> - N
On Sat, 26 Jun 2021 00:04:08 +1000, Michael Ellerman wrote:
> In raise_backtrace_ipi() we iterate through the cpumask of CPUs, sending
> each an IPI asking them to do a backtrace, but we don't wait for the
> backtrace to happen.
>
> We then iterate through the CPU mask again, and if any CPU hasn't
On Fri, 25 Jun 2021 14:53:37 +1000, Michael Ellerman wrote:
> There are patches in flight to break the dependency between asm/irq.h
> and linux/irqdomain.h, which would break compilation of vas.c because it
> needs the declaration of irq_create_mapping() etc.
>
> So add an explicit include of irqd
On Thu, 17 Jun 2021 13:55:06 -0400, Athira Rajeev wrote:
> On systems without any specific PMU driver support registered, running
> perf record causes Oops.
>
> The relevant portion from call trace:
>
> BUG: Kernel NULL pointer dereference on read at 0x0040
> Faulting instruction address: 0xc
On Thu, 24 Jun 2021 14:36:32 +0800, Jason Wang wrote:
> The ARRAY_SIZE macro is more compact and more formal in linux source.
Applied to powerpc/next.
[1/1] powerpc/sysfs: Replace sizeof(arr)/sizeof(arr[0]) with ARRAY_SIZE
https://git.kernel.org/powerpc/c/590e1e4254458455477e4e857cd00733280
On Thu, 24 Jun 2021 13:36:21 +0530, Vaibhav Jain wrote:
> Persistent memory devices like NVDIMMs can loose cached writes in case
> something prevents flush on power-fail. Such situations are termed as
> dirty shutdown and are exposed to applications as
> last-shutdown-state (LSS) flag and a dirty-s
On Thu, 13 May 2021 14:53:49 +0530, Vaibhav Jain wrote:
> In case performance stats for an nvdimm are not available, reading the
> 'perf_stats' sysfs file returns an -ENOENT error. A better approach is
> to make the 'perf_stats' file entirely invisible to indicate that
> performance stats for an nv
On Tue, 4 May 2021 17:43:43 +1000, Paul Mackerras wrote:
> This changes generic-compat-pmu.c so that it only uses architected
> events defined in Power ISA v3.0B, rather than event encodings which,
> while common to all the IBM Power Systems implementations, are
> nevertheless implementation-specif
On Tue, 22 Jun 2021 15:30:36 +1000, Nicholas Piggin wrote:
> copy-paste contains implicit "copy buffer" state that can contain
> arbitrary user data (if the user process executes a copy instruction).
> This could be snooped by another process if a context switch hits while
> the state is live. So c
On Tue, 1 Jun 2021 13:18:01 +0530, Naveen N. Rao wrote:
> It is sometimes desirable to run a command on all cpus in xmon. A
> typical scenario is to obtain the backtrace from all cpus in xmon if
> there is a soft lockup. Add rudimentary support for the same. The
> command to be run on all cpus shou
On Mon, 24 May 2021 17:32:27 +0530, Naveen N. Rao wrote:
> Both these config options are generally enabled in distro kernels.
> Enable the same in a few powerpc64 configs to get better coverage and
> testing.
Applied to powerpc/next.
[1/1] powerpc/configs: Enable STACK_TRACER and FTRACE_SYSCALLS
On Wed, 9 Jun 2021 14:30:24 +0530, Naveen N. Rao wrote:
> blrl corrupts the link stack. Instead use bctrl when making function
> calls from BPF programs.
Applied to powerpc/next.
[1/1] powerpc/bpf: Use bctrl for making function calls
https://git.kernel.org/powerpc/c/20ccb004bad659c186f90910
On Wed, 19 May 2021 16:17:16 +0530, Naveen N. Rao wrote:
> Various fixes and some code refactoring for kprobes on powerpc. The
> first patch fixes an invalid access if probing the first instruction in
> a kernel module. The rest are small cleanups. More details in the
> individual patches.
>
> - N
On Mon, 3 May 2021 12:58:11 -0500, Nathan Lynch wrote:
> RTAS_CLOCK_BUSY is unused, remove it.
Applied to powerpc/next.
[1/1] powerpc/rtas-rtc: remove unused constant
https://git.kernel.org/powerpc/c/4bfa5ddff924c2d5b2427f752515ca594dade19f
cheers
On Mon, 3 May 2021 21:53:29 -0500, Nathan Lynch wrote:
> Instead of making bare calls to get-sensor-state, use
> rtas_get_sensor(), which correctly handles busy and extended delay
> statuses.
Applied to powerpc/next.
[1/1] powerpc/pseries/dlpar: use rtas_get_sensor()
https://git.kernel.org/
On Wed, 23 Jun 2021 23:05:14 +1000, Michael Ellerman wrote:
> Commit a21d1becaa3f ("powerpc: Reintroduce is_kvm_guest() as a fast-path
> check") added is_kvm_guest() and changed kvm_para_available() to use it.
>
> is_kvm_guest() checks a static key, kvm_guest, and that static key is
> set in check
On Wed, 23 Jun 2021 23:04:54 +1000, Michael Ellerman wrote:
> When we boot from open firmware (OF) using PPC_OF_BOOT_TRAMPOLINE, aka.
> prom_init, we run parts of the kernel at an address other than the link
> address. That happens because OF loads the kernel above zero (OF is at
> zero) and we run
On Sun, 18 Apr 2021 13:10:03 +0530, Kajol Jain wrote:
> There is a spelling mistake "byes" -> "bytes" in a comment of
> function drc_pmem_query_stats(). Fix that typo.
Applied to powerpc/next.
[1/1] powerpc/papr_scm: trivial: fix typo in a comment
https://git.kernel.org/powerpc/c/d2827e5e2e
On Tue, 22 Jun 2021 22:17:46 -0700, Haren Myneni wrote:
> On PowerVM, the hypervisor defines the maximum buffer length for
> each NX request and the kernel exported this value via sysfs.
>
> This patch reads this value if the sysfs entry is available and
> is used to limit the request length.
App
On Wed, 23 Jun 2021 05:23:30 + (UTC), Christophe Leroy wrote:
> Trying to use a kprobe on ppc32 results in the below splat:
> BUG: Unable to handle kernel data access on read at 0x7c0802a6
> Faulting instruction address: 0xc002e9f0
> Oops: Kernel access of bad area, sig: 11 [#1]
>
On Mon, 19 Apr 2021 10:47:24 + (UTC), Christophe Leroy wrote:
> This series converts powerpc to generic PTDUMP.
>
> For that, we first need to add missing hugepd support
> to pagewalk and ptdump.
>
> v2:
> - Reworked the pagewalk modification to add locking and check ops->pte_entry
> - Modifi
On Fri, 4 Jun 2021 09:57:36 + (UTC), Christophe Leroy wrote:
> klimit is a global variable initialised at build time with the
> value of _end.
>
> This variable is never modified, so _end symbol can be used directly.
>
> Remove klimit.
Applied to powerpc/next.
[1/1] powerpc: Remove klimit
On Fri, 25 Jun 2021 14:49:09 + (UTC), Christophe Leroy wrote:
> trap->regs == 0x3000 is trap_is_scv()
>
> trap 0x500 is INTERRUPT_EXTERNAL
Applied to powerpc/next.
[1/1] powerpc/interrupt: Use names in check_return_regs_valid()
https://git.kernel.org/powerpc/c/b064037ea4104120418ccbf39
On Fri, 25 Jun 2021 14:31:46 + (UTC), Christophe Leroy wrote:
> Reduce #ifdefs a bit by making exit_must_hard_disable() return
> true on PPC32.
Applied to powerpc/next.
[1/1] powerpc/interrupt: Also use exit_must_hard_disable() on PPC32
https://git.kernel.org/powerpc/c/767e6e7130b288d85
On Fri, 4 Jun 2021 14:54:12 + (UTC), Christophe Leroy wrote:
> To better match booke version of SYSCALL_ENTRY macro, interchange
> r10 and r12 in the non booke version.
Applied to powerpc/next.
[1/4] powerpc/32: Interchange r10 and r12 in SYSCALL_ENTRY on non booke
https://git.kernel.or
On Fri, 25 Jun 2021 11:13:16 + (UTC), Christophe Leroy wrote:
> regs_set_return_msr() and regs_set_return_ip() have a copy
> of the code of set_return_regs_changed().
>
> Move up set_return_regs_changed() so it can be reused by
> regs_set_return_{msr/ip}
Applied to powerpc/next.
[1/2] powerp
On Thu, 29 Apr 2021 10:06:38 +0200, Arnd Bergmann wrote:
> gcc-11 points out that modifying local variables next to a
> longjmp/setjmp may cause undefined behavior:
>
> arch/powerpc/kexec/crash.c: In function 'crash_kexec_prepare_cpus.constprop':
> arch/powerpc/kexec/crash.c:108:22: error: variabl
Use is_kernel_text() and is_kernel_inittext() helper to simplify code,
also drop etext, _stext, _sinittext, _einittext declaration which
already declared in section.h.
Cc: Michael Ellerman
Cc: Benjamin Herrenschmidt
Cc: Paul Mackerras
Cc: linuxppc-dev@lists.ozlabs.org
Signed-off-by: Kefeng Wang
There are three head files(kallsyms.h, kernel.h and sections.h) which
include the kernel sections range check, let's make some cleanup and
unify them.
1. cleanup arch specific text/data check and fix address boundary check in
kallsyms.h
2. make all the basic kernel range check function into secti
38 matches
Mail list logo
