On Mon, 26 Sep 2022 07:57:23 +, Nicholas Miehlbradt wrote:
> There is support for DEBUG_PAGEALLOC on hash but not on radix.
> Add support on radix.
>
>
Applied to powerpc/next.
[1/4] powerpc/64s: Add DEBUG_PAGEALLOC for radix
On Mon, 26 Sep 2022 15:38:23 +1000, Nicholas Piggin wrote:
> The .toc section is not really intended for arbitrary data. Writable
> data in particular prevents making the TOC read-only after relocation.
> Move hcall_tracepoint_refcount into the .data section.
>
>
Applied to powerpc/next.
[1/1]
On Fri, 23 Sep 2022 13:30:04 +1000, Nicholas Piggin wrote:
> This adds basic POWER10_CPU option, which builds with -mcpu=power10.
>
>
Applied to powerpc/next.
[1/1] powerpc/64s: POWER10 CPU Kconfig build option
https://git.kernel.org/powerpc/c/4b2a9315f20d98576e25c9e4572e9a8e028d7aa2
On Thu, 8 Sep 2022 23:25:41 +1000, Nicholas Piggin wrote:
> On guest entry, vcpu->cpu and vcpu->arch.thread_cpu are set after
> disabling host irqs. On guest exit there is a window whre tick time
> accounting briefly enables irqs before these fields are cleared.
>
> Move them up to ensure they
On Wed, 21 Sep 2022 11:41:02 +1000, Nicholas Piggin wrote:
> Big-endian GENERIC_CPU supports 970, but builds with -mcpu=power5.
> POWER5 is ISA v2.02 whereas 970 is v2.01 plus Altivec. 2.02 added
> the popcntb instruction which a compiler might use.
>
> Use -mcpu=power4.
>
>
> [...]
Applied to
On Mon, 26 Sep 2022 17:02:50 -0500, Nathan Lynch wrote:
> At boot time, it is not necessary to delay between polls of
> cpu_callin_map when waiting for a kicked CPU to come up. Remove the
> delay intervals, but preserve the overall deadline (five seconds).
>
> At run time, the first poll result
On Mon, 26 Sep 2022 08:16:41 -0500, Nathan Lynch wrote:
> Add two new lockdown reasons for use in powerpc's pseries platform
> code.
>
> The pseries platform allows hardware-level error injection via certain
> calls to the RTAS (Run Time Abstraction Services) firmware. ACPI-based
> error
On Fri, 16 Sep 2022 23:15:23 +1000, Michael Ellerman wrote:
> Currently powerpc selects HAVE_EFFICIENT_UNALIGNED_ACCESS in all cases
> but one. The exception is if the kernel is being built little endian and
> explicitly targetted for Power7.
>
> The combination of Power7 an
On Fri, 30 Sep 2022 18:27:04 +1000, Michael Ellerman wrote:
> Create a hardware description string, which we will use to record
> various details of the hardware platform we are running on.
>
> Print the accumulated description at boot, and use it to set the generic
> description w
On Wed, 28 Sep 2022 23:09:41 +1000, Michael Ellerman wrote:
> The bulk of this was moved/reworded in:
> 57f266497d81 ("powerpc: Use gas sections for arranging exception vectors")
>
> And now appears around line 700 in arch/powerpc/kernel/exceptions-64s.S.
>
>
Ap
On Mon, 19 Sep 2022 15:27:55 +1000, Michael Ellerman wrote:
> The original microwatt submission[1] included some early debug code for
> using the Microwatt "potato" UART.
>
> The series that was eventually merged switched to using a standard UART,
> and so doesn't nee
On Wed, 28 Sep 2022 23:09:51 +1000, Michael Ellerman wrote:
> No toolchain we support should be generating stabs debug information
> anymore. Drop the sections entirely from our linker scripts.
>
> We removed all the manual stabs annotations in commit
> 12318163737c ("powerpc/
On Thu, 29 Sep 2022 15:15:17 +1000, Michael Ellerman wrote:
> Make sure the ultravisor code at least gets some build testing by
> enabling it in powernv_defconfig.
>
>
Applied to powerpc/next.
[1/1] powerpc/configs: Enable PPC_UV in powernv_defconfig
https://git.kernel.o
On Wed, 28 Sep 2022 23:09:12 +1000, Michael Ellerman wrote:
> This used to be about the 0x4300 handler, but that was moved in commit
> da2bc4644c75 ("powerpc/64s: Add new exception vector macros").
>
> Note that "STAB" here refers to "Segment Table" not t
On Tue, 13 Sep 2022 22:45:45 +1000, Michael Ellerman wrote:
> In interrupt_64.S, formerly entry_64.S, there are two toc entries
> created for sys_call_table and compat_sys_call_table.
>
> These are no longer used, since the system call entry was converted from
> asm to C,
On Fri, 16 Sep 2022 23:14:21 +1000, Michael Ellerman wrote:
> Add a check that STRICT_ALIGN_SIZE is aligned to at least PAGE_SIZE.
>
> That then makes the alignment to PAGE_SIZE immediately after the
> alignment to STRICT_ALIGN_SIZE redundant, so remove it.
>
>
Applied to p
On Sat, 3 Sep 2022 22:36:39 +1000, Michael Ellerman wrote:
> On powerpc there are two ways for huge pages to be represented in the
> top level page table, aka PGD (Page Global Directory).
>
> If the address space mapped by an individual PGD entry does not
> correspond to a given
On Wed, 28 Sep 2022 01:04:18 +1000, Michael Ellerman wrote:
> Now that the stack frame regs marker is only 32-bits it is not as
> obvious in memory dumps and easier to miss, eg:
>
> c4733e40 ||
> c4733e50 0
On Thu, 29 Sep 2022 12:15:02 +0200, Lukas Bulwahn wrote:
> Clean up config files by:
> - removing configs that were deleted in the past
> - removing configs not in tree and without recently pending patches
> - adding new configs that are replacements for old configs in the file
>
> For some
On Fri, 23 Sep 2022 17:32:53 +0800, Li Huafei wrote:
> I found a null pointer reference in arch_prepare_kprobe():
>
> # echo 'p cmdline_proc_show' > kprobe_events
> # echo 'p cmdline_proc_show+16' >> kprobe_events
> [ 67.278533][ T122] Kernel attempted to read user page (0) - exploit
>
On Mon, 12 Sep 2022 12:20:31 +0530, Hari Bathini wrote:
> Since commit e641eb03ab2b0 ("powerpc: Fix up the kdump base cap to
> 128M") memory for kdump kernel has been reserved at an offset of
> 128MB. This held up well for a long time before running into boot
> failure on LPARs having a lot of
On Tue, 27 Sep 2022 18:29:27 -0700, Haren Myneni wrote:
> The data storage interrupt (DSI) error will be generated when the
> paste operation is issued on the suspended Nest Accelerator (NX)
> window due to NX state changes. The hypervisor expects the
> partition to ignore this error during page
On Wed, 28 Sep 2022 18:57:33 -0700, Haren Myneni wrote:
> Generally the hypervisor decides to allocate a window on different
> VAS instances. But if the user space wishes to allocate on the
> current VAS instance where the process is executing, the kernel has
> to pass associativity domain IDs to
On Thu, 22 Sep 2022 01:27:07 -0700, Haren Myneni wrote:
> When the migration is initiated, the hypervisor changes VAS
> mappings as part of pre-migration event. Then the OS gets the
> migration event which closes all VAS windows before the migration
> starts. NX generates continuous faults until
On Tue, 20 Sep 2022 14:22:59 +0200, David Hildenbrand wrote:
> As it seems to be rather unclear if/when to use BUG(), BUG_ON(),
> VM_BUG_ON(), WARN_ON_ONCE(), ... let's try to document the result of a
> recent discussion.
>
> Details can be found in patch #1.
>
> RFC -> v1:
> *
On Mon, 19 Sep 2022 19:01:25 +0200, Christophe Leroy wrote:
> CONFIG_PPC_FSL_BOOKE doesn't exist. Should be CONFIG_FSL_BOOKE.
>
>
Applied to powerpc/next.
[01/19] powerpc/Kconfig: Fix non existing CONFIG_PPC_FSL_BOOKE
On Wed, 7 Sep 2022 12:05:01 +0200, Christophe Leroy wrote:
> PAGE_KERNEL_TEXT, PAGE_KERNEL_EXEC and PAGE_AGP are the same
> for all powerpcs.
>
> Remove duplicated definitions.
>
>
Applied to powerpc/next.
[1/1] powerpc: Reduce redundancy in pgtable.h
On Wed, 7 Sep 2022 12:05:21 +0200, Christophe Leroy wrote:
> Avoid multi-lines to help getting a complete view when using
> grep. They still remain under the 100 chars limit.
>
>
Applied to powerpc/next.
[1/1] powerpc: Make PAGE_KERNEL_xxx macros grep-friendly
On Tue, 20 Sep 2022 08:41:08 +0200, Christophe Leroy wrote:
> This partialy reapply commit ef5b570d3700 ("powerpc/irq: Don't
> open code irq_soft_mask helpers") which was reverted by
> commit 684c68d92e2e ("Revert "powerpc/irq: Don't open code
> irq_soft_mask helpers"")
>
>
On Tue, 20 Sep 2022 19:36:42 +0200, Christophe Leroy wrote:
> In addition to checking whether a page is reserved before allocating
> it to highmem, verify that it is valid memory.
>
> Otherwise the kernel Oopses as below:
>
> [0.00] mem auto-init: stack:off, heap alloc:off, heap free:off
On Mon, 5 Sep 2022 11:38:25 +0200, Christophe Leroy wrote:
> update_mmu_cache() voids when hash page tables are not used.
> On PPC32 that means when MMU_FTR_HPTE_TABLE is not defined.
> On PPC64 that means when RADIX is enabled.
>
> Rename core part of update_mmu_cache() as __update_mmu_cache()
>
On Wed, 7 Sep 2022 11:34:44 +0200, Christophe Leroy wrote:
> linux/hugetlb.h has a fallback pgd_huge() macro for when
> pgd_huge is not defined.
>
> Remove the powerpc redundant definitions.
>
>
Applied to powerpc/next.
[1/2] powerpc/nohash: Remove pgd_huge() stub
On Thu, 25 Aug 2022 07:26:57 +, cgel@gmail.com wrote:
> From: ye xingchen
>
> Return the value vas_register_coproc_api() directly instead of storing it
> in another redundant variable.
>
>
Applied to powerpc/next.
[1/1] powerpc/pseries/vas: Remove the unneeded result variable
On Thu, 8 Sep 2022 12:54:40 +0530, Aneesh Kumar K.V wrote:
> Powerpc architecture supports 16GB hugetlb pages with hash translation. For 4K
> page size, this is implemented as a hugepage directory entry at PGD level and
> for 64K it is implemented as a huge page pte at PUD level
>
> With 16GB
On Mon, 4 Jul 2022 12:08:51 +0530, Aneesh Kumar K.V wrote:
> For both CONFIG_NUMA enabled/disabled use mem_topology_setup to
> update max/min_low_pfn.
>
> This also add min_low_pfn update to CONFIG_NUMA which was initialized
> to zero before.
>
>
> [...]
Applied to powerpc/next.
[1/1]
On Tue, 6 Sep 2022 07:20:06 +, cgel@gmail.com wrote:
> From: ye xingchen
>
> Return the value opal_npu_spa_clear_cache() directly instead of storing
> it in another redundant variable.
>
>
Applied to powerpc/next.
[1/1] ocxl: Remove the unneeded result variable
On Wed, 21 Sep 2022 20:22:53 +0530, Athira Rajeev wrote:
> For PERF_SAMPLE_BRANCH_STACK sample type, different branch_sample_type
> ie branch filters are supported. The branch filters are requested via
> event attribute "branch_sample_type". Multiple branch filters can be
> passed in event
On Wed, 7 Sep 2022 13:49:41 +0530, Aneesh Kumar K.V wrote:
> This function does the hash page table update. Hence rename it to
> indicate this better to avoid confusion with flush_pmd_tlb_range()
>
>
Applied to powerpc/next.
[1/1] powerpc/mm/book3s/hash: Rename flush_tlb_pmd_range
On Tue, 16 Aug 2022 19:25:17 -0300, Fabiano Rosas wrote:
> We used to have a workaround[1] for a hang during migration that was
> made ineffective when we converted the decrementer expiry to be
> relative to guest timebase.
>
> The point of the workaround was that in the absence of an explicit
>
"Sven Peter" writes:
> On Sun, Oct 2, 2022, at 16:07, Arminder Singh wrote:
>> Hi,
>>
>>> #define REG_MTXFIFO0x00
>>> #define REG_MRXFIFO0x04
>>> #define REG_SMSTA 0x14
>>> +#define REG_IMASK 0x18
>>
>>> This doesn't seem to be aligned correctly, this file seems to use a tab
"Arnd Bergmann" writes:
> On Wed, Sep 28, 2022, at 2:15 PM, Michael Ellerman wrote:
>
>> But I think it makes more sense to do the same as mmap2() and pass the
>> 4K offset through, and pass shift = PAGE_SHIFT - 12. I also borrowed the
>> "off_4k&quo
Lukas Bulwahn writes:
> On Fri, Sep 30, 2022 at 9:42 AM Michael Ellerman wrote:
>>
>> Lukas Bulwahn writes:
>> > Clean up config files by:
>> > - removing configs that were deleted in the past
>> > - removing configs not in tree and without re
Michal Suchánek writes:
> On Thu, Sep 29, 2022 at 05:16:40PM -0500, Nathan Lynch wrote:
>> Haren Myneni writes:
>> > Generally the hypervisor decides to allocate a window on different
>> > VAS instances. But if the user space wishes to allocate on the
>> > current VAS instance where the process
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:IBM,FW860.42 (SV860_138) hv:phyp
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v3: Drop quotes
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... POWER8E (raw) 0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4
1 file changed, 4 insertions(+)
v3: Drop "cpu:" and &
ed by qemu) POWER9 (raw) 0x4e1200 0xf05
of:SLOF,git-5b4c5a pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20 insertions(+), 1 deletion(-)
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... 0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
v3: Drop "lpvr:
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: IBM,8247-22L
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
v3: Drop "model:
Lukas Bulwahn writes:
> Clean up config files by:
> - removing configs that were deleted in the past
> - removing configs not in tree and without recently pending patches
> - adding new configs that are replacements for old configs in the file
>
> For some detailed information, see Link.
>
Christophe Leroy writes:
> Le 01/09/2022 à 10:54, ruanjinjie a écrit :
>> [Vous ne recevez pas souvent de courriers de ruanjin...@huawei.com.
>> Découvrez pourquoi ceci est important à
>> https://aka.ms/LearnAboutSenderIdentification ]
>>
>> When build Linux kernel, encounter the following
Nathan Lynch writes:
> Michael Ellerman writes:
>
>> Add firmware version details to the dump stack arch description, which
>> is printed in case of an oops.
>>
>> Currently /hypervisor only exists on KVM, so if we don't find that
>> look for something t
Nathan Lynch writes:
> Michael Ellerman writes:
>> Create a hardware description string, which we will use to record
>> various details of the hardware platform we are running on.
>>
>> Print the accumulated description at boot, and use it to set the generic
>
Nathan Lynch writes:
> Michael Ellerman writes:
>> Add firmware version details to the hardware description, which is
>> printed at boot and in case of an oops.
>>
>> Use /hypervisor if we find it, though currently it only exists if we're
>> running under
Matthew Wilcox writes:
> On Tue, Sep 27, 2022 at 09:17:20AM +0800, Zorro Lang wrote:
>> Hi mm and ppc list,
>>
>> Recently I started to hit a kernel panic [2] rarely on *ppc64le* with *1k
>> blocksize* ext4. It's not easy to reproduce, but still has chance to trigger
>> by loop running
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:'phyp'
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v2: Use
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... cpu:'POWER8E (raw)' pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc
(emulated by qemu)' cpu:'POWER8 (raw)'
pvr:0x4d0200 lpvr:0xf04 of:'SLOF,HEAD' machine:pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20
Michael Ellerman writes:
> Create a hardware description string, which we will use to record
> various details of the hardware platform we are running on.
>
> Print the accumulated description at boot, and use it to set the generic
> description which is printed in oopses.
>
&
Add OPAL version details to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 22 ++
1 file changed, 22 insertions(+)
v2: Use
(emulated by qemu)' cpu:'POWER8 (raw)'
pvr:0x4d0200 lpvr:0xf04 of:'SLOF,HEAD' machine:pSeries
printk: bootconsole [udbg0] enabled
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup-common.c | 19 ++-
2 files changed, 20
Add the PVR and CPU name to the hardware description, which is printed
at boot and in case of an oops.
eg: Hardware name: ... cpu:'POWER8E (raw)' pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc
re running under PowerVM.
Failing that look for "ibm,fw-net-version" which is seen on PowerVM
going back to at least Power6.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:'phyp'
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 30 ++
If we detect a logical PVR add that to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch
Add the model of the machine we're on to the hardware description, which
is printed at boot and in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git
Arnaldo Carvalho de Melo writes:
> Em Wed, Sep 21, 2022 at 08:22:54PM +0530, Athira Rajeev escreveu:
>> commit b55878c90ab9 ("perf test: Add test for branch stack sampling")
>> added test for branch stack sampling. There is a sanity check in the
>> beginning to skip the test if the hardware
Make sure the ultravisor code at least gets some build testing by
enabling it in powernv_defconfig.
Signed-off-by: Michael Ellerman
---
arch/powerpc/configs/powernv_defconfig | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/powerpc/configs/powernv_defconfig
b/arch/powerpc/configs
Alistair Popple writes:
> Michael Ellerman writes:
>> Alistair Popple writes:
>>> When the CPU tries to access a device private page the migrate_to_ram()
>>> callback associated with the pgmap for the page is called. However no
>>> reference is taken on the f
Alistair Popple writes:
> When the CPU tries to access a device private page the migrate_to_ram()
> callback associated with the pgmap for the page is called. However no
> reference is taken on the faulting page. Therefore a concurrent
> migration of the device private page can free the page and
-version
seems to be a full path so is too long to add to the description.
eg: Hardware name: ... of:'IBM,FW860.42 (SV860_138)' hv:phyp
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/pseries/setup.c | 36 ++
1 file changed, 36 insertions(+)
diff --git a/arch
Add the PVR and CPU name to the dump stack arch description, which is
printed in case of an oops.
eg: Hardware name: ... POWER8E (raw) pvr:0x4b0201
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/kernel/prom.c
Add OPAL version details to the dump stack arch description, which is
printed in case of an oops.
eg: Hardware name: ... opal:v6.2
Signed-off-by: Michael Ellerman
---
arch/powerpc/platforms/powernv/setup.c | 26 ++
1 file changed, 26 insertions(+)
diff --git a/arch
As soon as we know the name of the machine description we're using,
add it to the dump stack arch description, which is printed in case of
an oops.
eg: Hardware name: ... machine:pSeries
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/setup.h | 2 ++
arch/powerpc/kernel/setup
Add the model of the machine we're on to the dump stack arch
description, which is printed in case of an oops.
eg: Hardware name: model:'IBM,8247-22L'
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 19 +++
1 file changed, 19 insertions(+)
diff --git a/arch
If we detect a logical PVR add that to the dump stack arch
description, which is printed in case of an oops.
eg: Hardware name: ... lpvr:0xf04
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/prom.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/arch/powerpc
No toolchain we support should be generating stabs debug information
anymore. Drop the sections entirely from our linker scripts.
We removed all the manual stabs annotations in commit
12318163737c ("powerpc/32: Remove remaining .stabs annotations").
Signed-off-by: Michael Ellerman
The bulk of this was moved/reworded in:
57f266497d81 ("powerpc: Use gas sections for arranging exception vectors")
And now appears around line 700 in arch/powerpc/kernel/exceptions-64s.S.
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/exceptions-64s.S | 10 --
1 fi
This used to be about the 0x4300 handler, but that was moved in commit
da2bc4644c75 ("powerpc/64s: Add new exception vector macros").
Note that "STAB" here refers to "Segment Table" not the debug format.
Signed-off-by: Michael Ellerman
---
arch/powerpc/kernel/
Rohan McLure writes:
> Syscall handlers should not be invoked internally by their symbol names,
> as these symbols defined by the architecture-defined SYSCALL_DEFINE
> macro. Move the compatibility syscall definition for mmap2 to
> syscalls.c, so that all mmap implementations can share a helper
Rohan McLure writes:
> Remove explicit clearing of the high order-word of user parameters when
> handling compatibility syscalls in system_call_exception. The
> COMPAT_SYSCALL_DEFINEx macros handle this clearing through an
> explicit cast to the signature type of the target handler.
||
c4733eb0 ||
So make it upper case to make it stand out a bit more:
c4733e70 53474552 |SGER|
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm
.|
Signed-off-by: Michael Ellerman
---
arch/powerpc/include/asm/ptrace.h | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/powerpc/include/asm/ptrace.h
b/arch/powerpc/include/asm/ptrace.h
index 6c23d1d25dc7..2efec6d87049 100644
--- a/arch/powerpc/include/asm/ptrace.h
+++ b/arch/power
cgel@gmail.com writes:
> From: Lv Ruyi
>
> This function fsl_msi_setup_hwirq() seems to return zero on success and
> non-zero on failure, but it returns zero in error handing path.
I agree it seems wrong, but I can't be sure the current code is wrong,
so unless you're able to test this on
Christophe Leroy writes:
> Le 26/09/2022 à 05:40, Nicholas Piggin a écrit :
>> Using a 32-bit constant for this marker allows it to be loaded with
>> two ALU instructions, like 32-bit. This avoids a TOC entry and a
>> TOC load that depends on the r2 value that has just been loaded from
>> the
Haren Myneni writes:
> DSI error will be generated when the paste operation is issued on
> the suspended NX window due to NX state changes. The hypervisor
Please spell out DSI and NX on the first usage.
> expects the partition to ignore this error during page pault
> handling. To differentiate
Christophe Leroy writes:
> Hi Dmitry
>
> Le 25/09/2022 à 07:06, Dmitry Torokhov a écrit :
>> Hi Michael, Nick,
>>
>> I was wondering if PIKA Warp board still relevant. The reason for my
>> question is that I am interested in dropping legacy gpio APIs,
>> especially OF-specific ones, in favor of
On Tue, 6 Sep 2022 11:03:13 +1000, Michael Ellerman wrote:
> Currently in pas_pci_init() a reference to the root node is leaked due
> to a missing of_node_put(). Instead just use of_root directly.
>
> Note that converting to of_find_compatible_node(NULL, ...) would
> not be enti
On Tue, 6 Sep 2022 14:17:03 +, Zheng Yongjun wrote:
> After using 'np' returned by of_find_node_by_path(), of_node_put()
> need be called to decrease the refcount.
>
>
Applied to powerpc/next.
[1/1] powerpc/powernv: add missing of_node_put() in opal_export_attrs()
On Thu, 1 Sep 2022 21:03:34 +1000, Nicholas Piggin wrote:
> Allow PTE changes to avoid flushing the TLB when access permissions are
> being relaxed, the dirty bit is being set, and the accessed bit is being
> changed.
>
> Relaxing access permissions and setting dirty and accessed bits do not
>
On Tue, 6 Sep 2022 22:32:13 +0100, Gustavo A. R. Silva wrote:
> Fix the following fallthrough warning:
>
> arch/powerpc/platforms/85xx/mpc85xx_cds.c:161:3: warning: unannotated
> fall-through between switch labels [-Wimplicit-fallthrough]
>
>
Applied to powerpc/next.
[1/1] powerpc: Fix
On Wed, 7 Sep 2022 17:01:11 -0500, Nathan Lynch wrote:
> At the time this was submitted by Leonardo, I confirmed -- or thought
> I had confirmed -- with PowerVM partition firmware development that
> the following RTAS functions:
>
> - ibm,get-xive
> - ibm,int-off
> - ibm,int-on
> - ibm,set-xive
>
On Tue, 13 Sep 2022 15:50:20 +0800, Gaosheng Cui wrote:
> This series contains a few cleanup patches, to remove unused
> declarations which have been removed. Thanks!
>
> Gaosheng Cui (9):
> powerpc/xmon: remove unused ppc_parse_cpu() declaration
> powerpc/spufs: remove orphan declarations
Christophe Leroy writes:
> Le 19/09/2022 à 16:01, Nicholas Piggin a écrit :
>> Using a 16-bit constant for this marker allows it to be loaded with
>> a single 'li' instruction. On 64-bit this avoids a TOC entry and a
>> TOC load that depends on the r2 value that has just been loaded from
>> the
Paul Moore writes:
> On Thu, Sep 22, 2022 at 3:38 PM Nathan Lynch wrote:
>>
>> The error injection facility on pseries VMs allows corruption of
>> arbitrary guest memory, potentially enabling a sufficiently privileged
>> user to disable lockdown or perform other modifications of the running
>>
Paul Moore writes:
> On Thu, Sep 22, 2022 at 3:38 PM Nathan Lynch wrote:
>>
>> The /proc/powerpc/ofdt interface allows the root user to freely alter
>> the in-kernel device tree, enabling arbitrary physical address writes
>> via drivers that could bind to malicious device nodes, thus making it
int kvm_arch_check_processor_compat(void)
> {
> - return kvmppc_core_check_processor_compat();
> + return 0;
> }
The actual change seems OK. I gave it a quick test boot and ran some
VMs, everything seems to work as before.
Acked-by: Michael Ellerman (powerpc)
cheers
David Hildenbrand writes:
> Unused, let's drop it.
>
> Signed-off-by: David Hildenbrand
> ---
> arch/powerpc/kernel/prom_init.c | 6 --
> 1 file changed, 6 deletions(-)
Thanks. I'll take this one via the powerpc tree, and the others can go
via wherever?
cheers
> diff --git
1501 - 1600 of 14982 matches
Mail list logo
