[PATCH v7 6/9] powerpc/pseries: Wakeup hvpipe FD when the payload is pending

2025-09-11 Thread Haren Myneni
The user space polls on the wait_queue for the payload from the specific source. The hypervisor interrupts the OS when the pipe status for the specific source is changed such as payload is available for the partition or pipe to the source is closed. The OS retrieves the HVPIPE event message with ch

Re: [PATCH v2 2/7] mm: introduce local state for lazy_mmu sections

2025-09-11 Thread Kevin Brodsky
On 10/09/2025 17:37, David Hildenbrand wrote: >> >> Somewhat, but in the regular case where enter() is called followed by >> leave() there is really no complexity for the caller, just an extra >> local variable. >> >> There are complications where we want to exit lazy_mmu temporarily, as >> in mm/k

Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout

2025-09-11 Thread Matthew Wilcox
On Wed, Sep 10, 2025 at 03:10:05PM +0200, Linus Walleij wrote: > This is is done so that we can unmap *most* of the kernel > memory but *keep* the VMALLOC area, so that e.g. exceptions > can still execute and save to stack when they occur, and we can > call into the kernel to execute said exception

[PATCH v17 09/12] mm: Provide address parameter to p{te,md,ud}_user_accessible_page()

2025-09-11 Thread Andrew Donnellan
From: Rohan McLure On several powerpc platforms, a page table entry may not imply whether the relevant mapping is for userspace or kernelspace. Instead, such platforms infer this by the address which is being accessed. Add an additional address argument to each of these routines in order to prov

Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout

2025-09-11 Thread Arnd Bergmann
On Wed, Sep 10, 2025, at 16:04, Matthew Wilcox wrote: > On Wed, Sep 10, 2025 at 03:10:05PM +0200, Linus Walleij wrote: >> >> This in practice means the area 0xf100-0x >> which also includes the high exception vectors that must for >> natural reasons also be kept in the mapping. >> What

[RFC V2 6/8] powerpc: Prepare for IRQ entry exit

2025-09-11 Thread Mukesh Kumar Chaurasiya
Copy all the functions from interrupt.h to arch specific entry-common.h file as it will be a part of common now. No functional change intended here. Signed-off-by: Mukesh Kumar Chaurasiya --- arch/powerpc/include/asm/entry-common.h | 420 1 file changed, 420 insertions(

[PATCH 05/14] paravirt: remove asm/paravirt_api_clock.h

2025-09-11 Thread Juergen Gross
All architectures supporting CONFIG_PARAVIRT share the same contents of asm/paravirt_api_clock.h: #include So remove all incarnations of asm/paravirt_api_clock.h and remove the only place where it is included, as there asm/paravirt.h is included anyway. Signed-off-by: Juergen Gross --- arch

Re: [PATCH v2 2/7] mm: introduce local state for lazy_mmu sections

2025-09-11 Thread David Hildenbrand
Can't we just use an "enum lazy_mmu_state" and call it a day? I could envision something completely different for this type on s390, e.g. a pointer to a per-cpu structure. So I would really ask to stick with the current approach. This is indeed the motivation - let every arch do whatever it se

Re: [PATCH] defconfig: cleanup orphaned CONFIG_SCHED_DEBUG

2025-09-11 Thread Krzysztof Kozlowski
On 28/08/2025 12:38, Trevor Woerner wrote: > In commit b52173065e0a ("sched/debug: Remove CONFIG_SCHED_DEBUG") this > Kconfig option was removed since CONFIG_SCHED_DEBUG was made unconditional > by patches preceding it. > > Signed-off-by: Trevor Woerner I doubt anyone will pick up such patch tou

[PATCH v2] powerpc/32: Restore clearing of MSR[RI] at interrupt/syscall exit

2025-09-11 Thread Christophe Leroy
Commit 13799748b957 ("powerpc/64: use interrupt restart table to speed up return from interrupt") removed the inconditional clearing of MSR[RI] when returning from interrupt into kernel. But powerpc/32 doesn't implement interrupt restart table hence still need MSR[RI] to be cleared. It could be ad

Re: [RFC PATCH v3 07/10] sched/core: Push current task from paravirt CPU

2025-09-11 Thread Shrikanth Hegde
On 9/11/25 10:36 PM, K Prateek Nayak wrote: Hello Shrikanth, On 9/11/2025 10:22 PM, Shrikanth Hegde wrote: +    if (is_cpu_paravirt(cpu)) +    push_current_from_paravirt_cpu(rq); Does this mean paravirt CPU is capable of handling an interrupt but may not be continuously available to ru

Re: [PATCH] ALSA: aoa: Remove redundant size arguments from strscpy()

2025-09-11 Thread Takashi Iwai
On Thu, 11 Sep 2025 23:43:22 +0200, Thorsten Blum wrote: > > The size parameter of strscpy() is optional if the destination buffer > has a fixed length and strscpy() can automatically determine its size > using sizeof(). This makes many explicit size arguments redundant. > > Remove them to shorte

[linux-next20250911]Kernel OOPs while running generic/256 on Pmem device

2025-09-11 Thread Venkat Rao Bagalkote
port_srp pseries_wdt [  163.372127] CPU: 22 UID: 0 PID: 130 Comm: kworker/22:0 Kdump: loaded Not tainted 6.17.0-rc5-next-20250911 #1 VOLUNTARY [  163.372142] Hardware name: IBM,9080-HEX Power11 (architected) 0x820200 0xf07 of:IBM,FW1110.01 (NH1110_069) hv:phyp pSeries [  163.372155] Wo

Re: [PATCH 1/2] powerpc/44x: Change GPIO driver to a proper platform driver

2025-09-11 Thread Madhavan Srinivasan
On Mon, 18 Aug 2025 14:17:34 +0200, Christophe Leroy wrote: > In order to drop legacy-of-mm-gpiochip dependency, first change the > 44x GPIO driver to a proper platform driver. > > Applied to powerpc/next. [1/2] powerpc/44x: Change GPIO driver to a proper platform driver https://git.kerne

Re: [PATCH] powerpc/ps3: Use str_write_read() in ps3stor_read_write_sectors()

2025-09-11 Thread Madhavan Srinivasan
On Tue, 19 Aug 2025 18:58:29 +0200, Thorsten Blum wrote: > Remove hard-coded strings by using the str_write_read() helper function > and silence the following Coccinelle/coccicheck warning reported by > string_choices.cocci: > > opportunity for str_write_read(write) > > > [...] Applied to pow

[PATCH v6 15/16] block-dma: properly take MMIO path

2025-09-11 Thread Leon Romanovsky
From: Leon Romanovsky Make sure that CPU is not synced and IOMMU is configured to take MMIO path by providing newly introduced DMA_ATTR_MMIO attribute. Reviewed-by: Keith Busch Signed-off-by: Leon Romanovsky --- block/blk-mq-dma.c | 13 +++-- include/linux/blk-mq-dma.h | 6 ++

Re: [PATCH] powerpc/vdso: Include asm/syscalls.h for sys_ni_syscall()

2025-09-11 Thread Madhavan Srinivasan
On Mon, 18 Aug 2025 11:26:44 +0200, Christophe Leroy wrote: > Include asm/syscalls.h to get the correct prototype for sys_ni_syscall() > > Applied to powerpc/next. [1/1] powerpc/vdso: Include asm/syscalls.h for sys_ni_syscall() https://git.kernel.org/powerpc/c/58f5382a482ba7313085de57767b

Re: [PATCH bpf-next v3 0/4] powerpc64/bpf: Add support for bpf arena and arena atomics

2025-09-11 Thread Madhavan Srinivasan
On Thu, 04 Sep 2025 15:38:31 +0530, Saket Kumar Bhaskar wrote: > This patch series introduces support for the PROBE_MEM32, > bpf_addr_space_cast and PROBE_ATOMIC instructions in the powerpc BPF JIT, > facilitating the implementation of BPF arena and arena atomics. > > All selftests related to bpf_

Re: [PATCH] powerpc: Remove duplicate definition for ppc_msgsnd_sync()

2025-09-11 Thread Madhavan Srinivasan
On Wed, 13 Aug 2025 17:53:18 +0530, Gautam Menghani wrote: > Remove duplicate definition of ppc_msgsnd_sync() introduced in commit > b87ac0218355 ('powerpc: Introduce msgsnd/doorbell barrier primitives'). > > No functional change intended. > > Applied to powerpc/next. [1/1] powerpc: Remove dup

Re: [PATCH] powerpc/8xx: Remove offset in SPRN_M_TWB

2025-09-11 Thread Madhavan Srinivasan
On Mon, 18 Aug 2025 11:24:22 +0200, Christophe Leroy wrote: > SPRN_M_TWB contains the address of task PGD minus an offset which > compensates the offset required when accessing the kernel PGDIR. > However, since commit ac9f97ff8b32 ("powerpc/8xx: Inconditionally use > task PGDIR in DTLB misses") an

Re: [PATCH v2 0/3] powerpc: Cleanup and convert to MSI parent domain

2025-09-11 Thread Madhavan Srinivasan
On Mon, 11 Aug 2025 11:28:53 +0200, Nam Cao wrote: > The initial implementation of PCI/MSI interrupt domains in the hierarchical > interrupt domain model used a shortcut by providing a global PCI/MSI > domain. > > This works because the PCI/MSI[X] hardware is standardized and uniform, but > it vio

Re: [PATCH] arch/powerpc: Remove support for older GCC and binutils

2025-09-11 Thread Madhavan Srinivasan
On Tue, 01 Jul 2025 12:50:07 +0200, Christophe Leroy wrote: > Commit 118c40b7b503 ("kbuild: require gcc-8 and binutils-2.30") raised > minimum GCC_VERSION and LD_VERSION. > > Simplify powerpc build accordingly. > > Applied to powerpc/next. [1/1] arch/powerpc: Remove support for older GCC and b

Re: [PATCH] powerpc/cpm2: Drop legacy-of-mm-gpiochip.h header

2025-09-11 Thread Madhavan Srinivasan
On Mon, 18 Aug 2025 14:14:36 +0200, Christophe Leroy wrote: > Remove legacy-of-mm-gpiochip.h header file. The above mentioned > file provides an OF API that's deprecated. There is no agnostic > alternatives to it and we have to open code the logic which was > hidden behind of_mm_gpiochip_add_data()

Re: [PATCH] gpio: mpc5200: Drop legacy-of-mm-gpiochip.h header

2025-09-11 Thread Madhavan Srinivasan
On Mon, 18 Aug 2025 14:42:24 +0200, Christophe Leroy wrote: > Remove legacy-of-mm-gpiochip.h header file. The above mentioned > file provides an OF API that's deprecated. There is no agnostic > alternatives to it and we have to open code the logic which was > hidden behind of_mm_gpiochip_add_data()

Re: [PATCH 0/4] PCI: Update error recovery documentation

2025-09-11 Thread Brian Norris
On Fri, Aug 29, 2025 at 09:25:00AM +0200, Lukas Wunner wrote: > The documentation on PCIe Advanced Error Reporting hasn't kept up with > code changes over the years. This series seeks to remedy as many issues > as I could find. > > Previous commits touching the documentation either prefixed the s

Re: [PATCH] PCI/AER: Fix NULL pointer access by aer_info

2025-09-11 Thread Bjorn Helgaas
[+cc Terry, Robert, CXL list, Smita, Dongdong] On Fri, Sep 05, 2025 at 02:25:27AM +0800, Vernon Yang wrote: > From: Vernon Yang > > The kzalloc(GFP_KERNEL) may return NULL, so all accesses to > aer_info->xxx will result in kernel panic. Fix it. > > Signed-off-by: Vernon Yang Applied to pci/ae

Re: [PATCH v6 03/16] dma-debug: refactor to use physical addresses for page mapping

2025-09-11 Thread Marek Szyprowski
On 10.09.2025 07:26, Leon Romanovsky wrote: > On Tue, Sep 09, 2025 at 10:37:48PM +0300, Leon Romanovsky wrote: >> On Tue, Sep 09, 2025 at 04:27:31PM +0300, Leon Romanovsky wrote: >>> From: Leon Romanovsky >> <...> >> >>> include/linux/page-flags.h | 1 + >> <...> >> >>> --- a/include/lin

Re: [PATCH v6 00/16] dma-mapping: migrate to physical address-based API

2025-09-11 Thread Marek Szyprowski
On 09.09.2025 15:27, Leon Romanovsky wrote: > From: Leon Romanovsky > > Changelog: > v6: > * Based on "dma-debug: don't enforce dma mapping check on noncoherent > allocations" patch. > * Removed some unused variables from kmsan conversion. > * Fixed missed ! in dma check. > v5: https://l

[PATCH] ALSA: aoa: Remove redundant size arguments from strscpy()

2025-09-11 Thread Thorsten Blum
The size parameter of strscpy() is optional if the destination buffer has a fixed length and strscpy() can automatically determine its size using sizeof(). This makes many explicit size arguments redundant. Remove them to shorten and simplify the code. No functional changes intended. Signed-off-

Re: [PATCH v2 2/7] mm: introduce local state for lazy_mmu sections

2025-09-11 Thread David Hildenbrand
On the other hand, with a pagefault_disabled-like approach, there is no way to instruct call {3} to fully exit lazy_mmu regardless of the nesting level. Sure there is, with a better API. See below. :) I meant while keeping the existing shape of the API but yes fair enough! Time to do it prop

Re: [RFC PATCH v3 07/10] sched/core: Push current task from paravirt CPU

2025-09-11 Thread K Prateek Nayak
Hello Shrikanth, On 9/11/2025 10:22 PM, Shrikanth Hegde wrote: >>> +    if (is_cpu_paravirt(cpu)) >>> +    push_current_from_paravirt_cpu(rq); >> >> Does this mean paravirt CPU is capable of handling an interrupt but may >> not be continuously available to run a task? > > When i run hackbench

Re: [PATCH v2 2/7] mm: introduce local state for lazy_mmu sections

2025-09-11 Thread Kevin Brodsky
On 11/09/2025 14:06, Alexander Gordeev wrote: > On Wed, Sep 10, 2025 at 06:11:54PM +0200, Kevin Brodsky wrote: > > Hi Kevin, > >> On 09/09/2025 16:38, Alexander Gordeev wrote: >>> Would that integrate well with LAZY_MMU_DEFAULT etc? >> Hmm... I though the idea is to use LAZY_MMU_* by archit

Re: [RFC PATCH v3 03/10] sched: Static key to check paravirt cpu push

2025-09-11 Thread Shrikanth Hegde
On 9/11/25 7:23 AM, Yury Norov wrote: On Wed, Sep 10, 2025 at 11:12:03PM +0530, Shrikanth Hegde wrote: CPUs are marked paravirt when there is contention for underlying physical CPU. The push mechanism and check for paravirt CPUs are in sched tick and wakeup. It should be close to no-op when

Re: [PATCH v2 2/7] mm: introduce local state for lazy_mmu sections

2025-09-11 Thread Alexander Gordeev
On Wed, Sep 10, 2025 at 06:11:54PM +0200, Kevin Brodsky wrote: Hi Kevin, > On 09/09/2025 16:38, Alexander Gordeev wrote: > > Would that integrate well with LAZY_MMU_DEFAULT etc? > Hmm... I though the idea is to use LAZY_MMU_* by architectures that > want to use it - at least that is

Re: [TECH TOPIC] Reaching consensus on CONFIG_HIGHMEM phaseout

2025-09-11 Thread Arnd Bergmann
On Thu, Sep 11, 2025, at 07:38, Andreas Larsson wrote: > > We have a upcoming SoC with support for up to 16 GiB of DRAM. When that is > used in LEON sparc32 configuration (using 36-bit physical addressing), a > removed CONFIG_HIGHMEM would be a considerable limitation, even after an > introduction

Re: [PATCH 00/14] paravirt: cleanup and reorg

2025-09-11 Thread Peter Zijlstra
On Thu, Sep 11, 2025 at 08:34:19AM +0200, Juergen Gross wrote: > Some cleanups and reorg of paravirt code and headers: > > - The first 2 patches should be not controversial at all, as they > remove just some no longer needed #include and struct forward > declarations. > > - The 3rd patch is r

Re: [RFC PATCH v3 05/10] sched/fair: Don't consider paravirt CPUs for wakeup and load balance

2025-09-11 Thread K Prateek Nayak
Hello Shrikanth, On 9/10/2025 11:12 PM, Shrikanth Hegde wrote: > @@ -8563,7 +8563,7 @@ select_task_rq_fair(struct task_struct *p, int > prev_cpu, int wake_flags) > if (!is_rd_overutilized(this_rq()->rd)) { > new_cpu = find_energy_efficient_cpu(p, prev_cpu); >