Hello Michael,
Do you have any feedback or comments regarding this patch?
Thanks,
Sourabh
On 08/06/23 14:52, Sourabh Jain wrote:
If the memory reservation process (memblock_reserve) fails to reserve
the memory, the reserve dump variable retains the dump area size.
Consequently, the size of the
Gautam Menghani writes:
> Remove an unnecessary piece of code that does an endianness conversion but
> does not use the result. The following warning was reported by Clang's
> static analyzer:
>
> arch/powerpc/sysdev/xics/ics-opal.c:114:2: warning: Value stored to
> 'server' is never read [deadcod
On 03.07.23 07:21, Michael Ellerman wrote:
On Fri, 05 May 2023 12:18:17 -0500, Rob Herring wrote:
Commit e4ab08be5b49 ("powerpc/isa-bridge: Remove open coded "ranges"
parsing") broke PASemi Nemo board booting. The issue is the ISA I/O
range was not getting mapped as the logic to handle no "range
On Thu, 25 May 2023 22:56:22 +0200, Uwe Kleine-König wrote:
> After commit b8a1a4cd5a98 ("i2c: Provide a temporary .probe_new()
> call-back type"), all drivers being converted to .probe_new() and then
> 03c835f498b5 ("i2c: Switch .probe() to not take an id parameter")
> convert back to (the new) .p
On Thu, 13 Apr 2023 08:16:42 +0200, Uwe Kleine-König wrote:
> While mpc5200b.dtsi contains a device that this driver can bind to, the
> only purpose of a bound device is to be used by the four exported functions
> mpc52xx_lpbfifo_submit(), mpc52xx_lpbfifo_abort(), mpc52xx_lpbfifo_poll()
> and mpc52
On Tue, 23 May 2023 21:50:53 +0200, Uwe Kleine-König wrote:
> After commit b8a1a4cd5a98 ("i2c: Provide a temporary .probe_new()
> call-back type"), all drivers being converted to .probe_new() and then
> 03c835f498b5 ("i2c: Switch .probe() to not take an id parameter") convert
> back to (the new) .p
On Sun, 19 Mar 2023 09:59:31 -0500, Rob Herring wrote:
> Replace open coded reading of CPU nodes' "reg" properties with
> of_get_cpu_hwid() dedicated for this purpose.
>
>
Applied to powerpc/next.
[1/1] powerpc: powermac: Use of_get_cpu_hwid() to read CPU node 'reg'
https://git.kernel.org
On Fri, 28 Apr 2023 18:12:40 -0400, Tom Rix wrote:
> For ppc64, gcc with W=1 reports
> arch/powerpc/platforms/cell/spu_base.c:330:17: error:
> suggest braces around empty body in an 'if' statement [-Werror=empty-body]
> 330 | ;
> | ^
> arch/powerpc/platform
On Mon, 05 Jun 2023 13:48:56 -0500, Timothy Pearson wrote:
> and PowerNV
>
> A build failure with CONFIG_HAVE_PCI=y set without PSERIES or POWERNV
> set was caught by the random configuration checker. Guard the sPAPR
> specific IOMMU functions on CONFIG_PPC_PSERIES || CONFIG_PPC_POWERNV.
>
>
>
On Fri, 09 Jun 2023 12:32:32 -0600, Rob Herring wrote:
> "ranges" is a standard property, and we have common helper functions
> for parsing it, so let's use the for_each_of_range() iterator.
>
>
Applied to powerpc/next.
[1/1] powerpc: mpc512x: Remove open coded "ranges" parsing
https://gi
On Sun, 19 Mar 2023 11:32:26 -0500, Rob Herring wrote:
> Replace open coded reading of "reg" and of_translate_address() calls with
> single call to of_address_to_resource().
>
>
Applied to powerpc/next.
[1/1] macintosh: Use of_address_to_resource()
https://git.kernel.org/powerpc/c/93cfa6f
On Fri, 09 Jun 2023 12:31:50 -0600, Rob Herring wrote:
> Use the recently added of_property_read_reg() helper to get the
> untranslated "reg" address value.
>
>
Applied to powerpc/next.
[1/1] powerpc: fsl: Use of_property_read_reg() to parse "reg"
https://git.kernel.org/powerpc/c/f892ac77
On Fri, 09 Jun 2023 12:32:38 -0600, Rob Herring wrote:
> "ranges" is a standard property with common parsing functions. Users
> shouldn't be implementing their own parsing of it. Refactor the FSL RapidIO
> "ranges" parsing to use of_range_to_resource() instead.
>
>
Applied to powerpc/next.
[1/1
On Sun, 21 May 2023 15:51:03 -0700, Randy Dunlap wrote:
> When CONFIG_SMP is not set, CONFIG_BROKEN_ON_SMP is set, and
> CONFIG_PCI is not set, there can be a kconfig warning:
>
> WARNING: unmet direct dependencies detected for PPC_INDIRECT_PCI
> Depends on [n]: PCI [=n]
> Selected by [y]:
>
On Fri, 09 Jun 2023 12:32:44 -0600, Rob Herring wrote:
> "ranges" is a standard property with common parsing functions. Users
> shouldn't be implementing their own parsing of it. Refactor the FSL RapidIO
> "ranges" parsing to use of_range_to_resource() instead.
>
> One change is the original code
On Wed, 14 Jun 2023 11:17:23 -0600, Rob Herring wrote:
> In some builds, the mpc52xx_pm_prepare()/lite5200_pm_prepare() functions
> generate stack size warnings. The addition of 'struct resource' in commit
> 2500763dd3db ("powerpc: Use of_address_to_resource()") grew the stack size
> and is blamed
On Fri, 09 Jun 2023 12:29:25 -0600, Rob Herring wrote:
> Use the recently added of_property_read_reg() helper to get the
> untranslated "reg" address value.
>
>
Applied to powerpc/next.
[1/1] macintosh: Use of_property_read_reg() to parse "reg"
https://git.kernel.org/powerpc/c/6f3bdbbeafb
On Wed, 10 May 2023 13:31:06 +1000, Rohan McLure wrote:
> v1 of this patch series available here:
> Link:
> https://lore.kernel.org/linuxppc-dev/20230508020120.218494-1-rmcl...@linux.ibm.com/
>
> The KCSAN sanitiser notifies programmers of instances where unmarked
> accesses to shared state has l
On Fri, 28 Apr 2023 21:35:03 -0700, Randy Dunlap wrote:
> Drop an unused and empty "config" entry for PPC_86xx.
> It has no keyword entries under it and the following line's
> "menuconfig" for the same Kconfig symbol is what kconfig uses.
>
>
Applied to powerpc/next.
[1/1] powerpc: delete empty
On Tue, 20 Jun 2023 00:32:58 -0400, Paul Gortmaker wrote:
> v1:
> https://lore.kernel.org/all/20230221194637.28436-1-paul.gortma...@windriver.com/
>
> v1 --> v2:
>-don't remove MPC8568MDS or P1021 or P1012 platforms as per discussion
>-drop commit #4 that removed kernel fragments still in
On Tue, 06 Jun 2023 23:24:41 +1000, Nicholas Piggin wrote:
> Since v2:
> - Add PPC_CREATE_STACK_FRAME() to abstract prologue differences.
> - Build fix.
> - Makefile tidy [Christophe]
> - Fix a missing SOB.
>
> Since v1:
> - Don't re-order 32-bit prologue.
> - Improve Kconfig conditional includes.
On Tue, 06 Jun 2023 16:48:30 +1000, Nicholas Piggin wrote:
> x86 removed -pipe in commit 437e88ab8f9e2 ("x86/build: Remove -pipe from
> KBUILD_CFLAGS") and the newer arm64 and riscv seem to have never used it,
> so that seems to be the way the world's going.
>
> Compile performance building defcon
On Tue, 06 Jun 2023 16:46:53 +1000, Nicholas Piggin wrote:
> This is a rebase of the series here. It's no longer a fix because
> the clang build issue got a minimal fix. A couple were merged, and
> I pulled the rest of the boot specific ones into this series.
>
> https://lore.kernel.org/linuxppc-d
On Tue, 06 Jun 2023 19:38:28 +1000, Nicholas Piggin wrote:
> This is a follow on from the series here
>
> https://lore.kernel.org/linuxppc-dev/20230505071850.228734-1-npig...@gmail.com/
>
> With feedback addressed and Christophe's -mprofile-kernel for BE added,
>
> https://lore.kernel.org/linuxp
On Fri, 09 Jun 2023 15:10:02 +1000, Nicholas Piggin wrote:
> Add --orphan-handlin for vdsos, and adjust vdso linker scripts to deal
> with orphan sections.
>
>
Applied to powerpc/next.
[1/1] powerpc/build: vdso linker warning for orphan sections
https://git.kernel.org/powerpc/c/8ad57add77
On Wed, 07 Jun 2023 20:10:24 +1000, Nicholas Piggin wrote:
> The refcount on mm is dropped before the coprocessor is detached.
>
>
Applied to powerpc/next.
[1/1] powerpc/64s: Fix VAS mm use after free
https://git.kernel.org/powerpc/c/b4bda59b47879cce38a6ec5a01cd3cac702b5331
cheers
On Tue, 06 Jun 2023 23:18:28 +1000, Nicholas Piggin wrote:
> LLVM assembler does not recognise 3-operand cmpi, use cmpwi.
>
>
Applied to powerpc/next.
[1/1] powerpc/32s: Fix LLVM SMP build
https://git.kernel.org/powerpc/c/31b4f69dbae810b13237a7e8c89a52a72fd492e2
cheers
On Thu, 08 Jun 2023 12:45:04 +1000, Nicholas Piggin wrote:
> Michael is merging KVM PPC patches via the powerpc tree and KVM topic
> branches. He doesn't necessarily have time to be across all of KVM so
> is reluctant to call himself maintainer, but for the mechanics of how
> patches flow upstream,
On Thu, 08 Jun 2023 08:04:44 -0400, Nayna Jain wrote:
> On PowerVM guest, variable data is prefixed with 8 bytes of timestamp.
> Extract ESL by stripping off the timestamp before passing to ESL parser.
>
>
Applied to powerpc/next.
[1/1] security/integrity: fix pointer to ESL data and its size o
On Tue, 30 May 2023 11:44:36 +0530, Naveen N Rao wrote:
> binutils v2.37 drops unused section symbols, which prevents recordmcount
> from capturing mcount locations in sections that have no non-weak
> symbols. This results in a build failure with a message such as:
> Cannot find symbol for se
On Fri, 09 Jun 2023 09:15:01 +0530, Naveen N Rao wrote:
> Ftrace on ppc32 expects a three instruction sequence at the beginning of
> each function when specifying -pg:
> mflrr0
> stw r0,4(r1)
> bl _mcount
>
> This is the case with all supported versions of gcc. Clang
On Wed, 17 May 2023 17:48:19 +1000, Michael Ellerman wrote:
> Ben no longer has time to do any maintenance of the powermac code. Mark
> it as orphan.
>
>
Applied to powerpc/next.
[1/1] powerpc: Mark powermac as orphan in MAINTAINERS
https://git.kernel.org/powerpc/c/b8d96bac4a50b8c8adb195e
On Wed, 31 May 2023 22:50:23 +1000, Michael Ellerman wrote:
> The powerpc section has a "F:" entry for drivers/macintosh, matching all
> files in or below drivers/macintosh. That is correct for the most part,
> but there are a couple of m68k-only drivers in the directory, so exclude
> those.
>
>
On Thu, 19 Jan 2023 17:22:50 +0900, Masahiro Yamada wrote:
> Commit e4412739472b ("Documentation: raise minimum supported version of
> binutils to 2.25") allows us to remove the checks for old binutils.
>
> There is no more user for ld-ifversion. Remove it as well.
>
>
Applied to powerpc/next.
On Tue, 13 Jun 2023 14:21:59 +0930, Joel Stanley wrote:
> Oliver mentioned this code was only kept around to support the VPL
> Power7 boxes. Now that they are all gone, remove the code.
>
> Build and boot tested in qemu only.
>
> Joel Stanley (3):
> powernv/pci: Remove ioda1 support
> powerpc
On Tue, 13 Jun 2023 12:16:41 -0500, Gaurav Batra wrote:
> When memory is dynamically added/removed, iommu_mem_notifier() is invoked.
> This
> routine traverses through all the DMA windows (DDW only, not default windows)
> to add/remove "direct" TCE mappings. The routines for this purpose are
> tce
On Thu, 08 Jun 2023 10:58:49 +0100, Colin Ian King wrote:
> Currently pointer iov is being dereferenced before the null check of iov
> which can lead to null pointer dereference errors. Fix this by moving the
> iov null check before the dereferencing.
>
> Detected using cppcheck static analysis:
>
On Mon, 05 Jun 2023 10:58:35 +0200, Christophe Leroy wrote:
> Looking at generated code for handle_signal32() shows calls to a
> function called __unsafe_save_user_regs.constprop.0 while user access
> is open.
>
> And that __unsafe_save_user_regs.constprop.0 function has two nops at
> the begining
On Fri, 26 May 2023 07:57:33 +0200, Christophe Leroy wrote:
> The following boottime error is encountered with SMP kernel:
>
> kcsan: improperly instrumented type=(0): arch_spin_unlock(&arch_spinlock)
> kcsan: improperly instrumented type=(0): spin_unlock(&test_spinlock)
> kcsan: improperly
On Mon, 05 Jun 2023 10:55:26 +0200, Christophe Leroy wrote:
> A disassembly of interrupt_exit_kernel_prepare() shows a useless read
> of MSR register. This is shown by r9 being re-used immediately without
> doing anything with the value read.
>
> c000e0e0: 60 00 00 00 nop
> c000e0e4:
On Fri, 12 May 2023 17:31:16 +0200, Christophe Leroy wrote:
> This series enables KCSAN on all powerpc.
>
> To do this, a fix is required to KCSAN core.
>
> Once that fix is done, the stubs can also be removed from xtensa.
>
> It would be nice if patch 1 could go in v6.4 as a fix, then patches 2
On Fri, 16 Jun 2023 13:48:35 +1000, Benjamin Gray wrote:
> v3: * Expose (H)DEXCR in ptrace as 64 bits
> * Remove build config for DEXCR, always enable NPHIE
> * Fix up documentation to reflect this
> * Some commit message fixes
>
> Previous versions:
> v2: https://lore.kernel.o
On Fri, 16 Jun 2023 16:38:10 +0530, Aneesh Kumar K.V wrote:
> This patch series implements changes required to support DAX vmemmap
> optimization for ppc64. The vmemmap optimization is only enabled with radix
> MMU
> translation and 1GB PUD mapping with 64K page size. The patch series also
> spli
On Thu, 15 Jun 2023 14:40:47 +0530, Aditya Gupta wrote:
> ppc_save_regs() skips one stack frame while saving the CPU register states.
> Instead of saving current R1, it pulls the previous stack frame pointer.
>
> When vmcores caused by direct panic call (such as `echo c >
> /proc/sysrq-trigger`),
Hi Everyone,
On 2023-06-08 08:34:48, Kautuk Consul wrote:
> - Enable CONFIG_HAVE_KVM_DIRTY_RING_ACQ_REL as ppc64 is weakly
> ordered.
> - Enable CONFIG_NEED_KVM_DIRTY_RING_WITH_BITMAP because the
> kvmppc_xive_native_set_attr is called in the context of an ioctl
> syscall and will call kvmpp
On Fri, 05 May 2023 12:18:17 -0500, Rob Herring wrote:
> Commit e4ab08be5b49 ("powerpc/isa-bridge: Remove open coded "ranges"
> parsing") broke PASemi Nemo board booting. The issue is the ISA I/O
> range was not getting mapped as the logic to handle no "ranges" was
> inverted. If phb_io_base_phys i
On Fri, 28 Apr 2023 21:35:19 -0700, Randy Dunlap wrote:
> Neither FSL_SOC_BOOKE nor PPC_86xx enables CONFIG_PCI by
> default, so it may be unset in some randconfigs.
> When that happens, FSL_ULI1575 may be set when it should not be
> since it is a PCI driver. When it is set, there are 3 kconfig
> w
On Thu, 27 Apr 2023 12:34:53 -0700, Nathan Chancellor wrote:
> When building the boot wrapper assembly files with clang after
> commit 648a1783fe25 ("powerpc/boot: Fix boot wrapper code generation
> with CONFIG_POWER10_CPU"), the following warnings appear for each file
> built:
>
> '-prefixed' i
On Fri, 19 May 2023 21:38:06 +1000, Michael Ellerman wrote:
> Commit 1e8fed873e74 ("powerpc: drop ranges for definition of
> ARCH_FORCE_MAX_ORDER") removed the limits on the possible values for
> ARCH_FORCE_MAX_ORDER.
>
> However removing the ranges entirely causes some common work flows to
> brea
On Thu, 11 May 2023 21:42:24 +1000, Michael Ellerman wrote:
> It was reported that soft dirty tracking doesn't work when using the
> Radix MMU.
>
> The tracking is supposed to work by clearing the soft dirty bit for a
> mapping and then write protecting the PTE. If/when the page is written
> to, a
On Mon, 15 May 2023 21:12:31 -0300, Jason Gunthorpe wrote:
> Now that power calls iommu_device_register() and populates its groups
> using iommu_ops->device_group it should not be calling
> iommu_group_remove_device().
>
> The core code owns the groups and all the other related iommu data, it
> wi
On Tue, 25 Apr 2023 12:28:29 +0530, Hari Bathini wrote:
> Since commit 85e031154c7c ("powerpc/bpf: Perform complete extra passes
> to update addresses"), two additional passes are performed to avoid
> space and CPU time wastage on powerpc. But these extra passes led to
> WARN_ON_ONCE() hits in bpf_
On Thu, 04 May 2023 12:59:13 -0500, Gaurav Batra wrote:
> When DMA window is backed by 2MB TCEs, the DMA address for the mapped
> page should be the offset of the page relative to the 2MB TCE. The code
> was incorrectly setting the DMA address to the beginning of the TCE
> range.
>
> Mellanox driv
On Fri, 05 May 2023 13:47:01 -0500, Gaurav Batra wrote:
> For an SR-IOV device, while enabling DDW, a new table is created and added
> at index 1 in the group. In the below 2 scenarios, the table is incorrectly
> referenced at index 0 (which is where the table is for default DMA window).
>
> 1. Wh
On Wed, 07 Jun 2023 10:56:00 +1000, Nicholas Piggin wrote:
> Switching mm and tinkering with current->active_mm should be done with
> irqs disabled. There is a path where exit_lazy_flush_tlb can be called
> with irqs enabled:
>
> exit_lazy_flush_tlb
> flush_type_needed
> __flush_all_mm
On Thu, 25 May 2023 09:34:54 -0500, Gaurav Batra wrote:
> As of now, in tce_freemulti_pSeriesLP(), there is no limit on how many TCEs
> are passed to H_STUFF_TCE hcall. This was not an issue until now. Newer
> firmware releases have started enforcing this requirement.
>
> The interface has been in
On Mon, 29 May 2023 16:43:36 +0530, Maninder Singh wrote:
> kallsyms_lookup which in turn calls for kallsyms_lookup_buildid()
> writes on index "KSYM_NAME_LEN - 1".
>
> Thus array size should be KSYM_NAME_LEN.
>
> for hexagon it was defined as "128" directly.
> and commit '61968dbc2d5d' changed d
On 09-06-23, 12:31, Rob Herring wrote:
> Use the recently added of_property_read_reg() helper to get the
> untranslated "reg" address value.
>
> Signed-off-by: Rob Herring
> ---
> drivers/cpufreq/pmac32-cpufreq.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/driv
> Jacob: Can you repeat bisection please? Why did you skip VMA lock-based
page fault commits in your bisection?
All skips were due to compile errors of the form:
make[3]: 'install_headers' is up to date.
In file included from ./include/linux/memcontrol.h:20,
from ./include/linux/s
Hi Michael.
Michael Schmitz - 01.07.23, 04:05:30 CEST:
> The RDB format description URL that appears in one of your messages
> from the 2012 thread has gone dead. I'll try to find it on Wayback
> later. In the meantime, I will submit a patch to fix the new bug ...
> We can has out details in the i
On 7/2/23 19:40, Jacob Young wrote:
>> Jacob: Can you repeat bisection please? Why did you skip VMA lock-based
> page fault commits in your bisection?
>
> All skips were due to compile errors of the form:
> make[3]: 'install_headers' is up to date.
> In file included from ./include/linux/memcontro
Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> After upgrading to kernel version 6.4.0 from 6.3.9, I noticed frequent but
> random crashes in a user space program. After a lot of reduction, I have
> come up with the following reproducer program:
>
> $ uname -a
> Linux ja
On Saturday 10 June 2023 09:35:21 Pali Rohár wrote:
> On Friday 05 May 2023 19:28:18 Pali Rohár wrote:
> > Freescale PCIe controllers on their PCIe Root Ports do not have any
> > mappable PCI BAR allocate from PCIe MEM.
> >
> > Information about 1MB window on BAR0 of PCIe Root Port was misleading
63 matches
Mail list logo
