On Wed May 8, 2024 at 11:36 PM AEST, Thomas Huth wrote:
> On 08/05/2024 14.58, Thomas Huth wrote:
> > On 08/05/2024 14.55, Thomas Huth wrote:
> >> On 08/05/2024 14.27, Nicholas Piggin wrote:
> >>> On Wed May 8, 2024 at 1:08 AM AEST, Thomas Huth wrote:
> On 04/05/2024 14.28, Nicholas Piggin
On Wed May 8, 2024 at 10:36 PM AEST, Michael Ellerman wrote:
> Gautam Menghani writes:
> > PAPR hypervisor has introduced three new counters in the VPA area of
> > LPAR CPUs for KVM L2 guest (see [1] for terminology) observability - 2
> > for context switches from host to guest and vice versa,
Christophe Leroy writes:
Hi Christian, hi Hari,
Le 04/04/2024 à 19:44, Christian Zigotzky a écrit :
Shall we use CONFIG_CRASH_DUMP to get int crashing_cpu = -1;?
Further information:
https://lists.ozlabs.org/pipermail/linuxppc-dev/2024-March/269985.html
On i.MX95, the XCVR uses a new PLL in the PHY, which is
General Purpose (GP) PLL. Add GP PLL configuration support
in the driver and add the 'pll_ver' flag to distinguish
different PLL on different platforms.
The XCVR also use PHY but limited for SPDIF only case
Add 'use_phy' flag to distinguish
When there are 'pll8k' and 'pll11k' clock existing, the clock
source of 'phy_clk' can be changed for different sample rate
requirement.
Signed-off-by: Shengjiu Wang
---
sound/soc/fsl/fsl_xcvr.c | 8
1 file changed, 8 insertions(+)
diff --git a/sound/soc/fsl/fsl_xcvr.c
On i.MX95 wakeup domain, there is one instance of Audio XCVR
supporting SPDIF mode with a connection to the Audio XCVR physical
interface.
Shengjiu Wang (4):
ASoC: dt-bindings: fsl,xcvr: Add compatible string for i.MX95
ASoC: dt-bindings: fsl,xcvr: Add two PLL clock sources
ASoC: fsl_xcvr:
Add two PLL clock sources, they are the parent clocks of the root clock
one is for 8kHz series rates, named as 'pll8k', another one is for
11kHz series rates, named as 'pll11k'. They are optional clocks,
if there are such clocks, then the driver can switch between them to
support more accurate
Add compatible string "fsl,imx95-xcvr" for i.MX95 platform.
Signed-off-by: Shengjiu Wang
---
Documentation/devicetree/bindings/sound/fsl,xcvr.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/sound/fsl,xcvr.yaml
On Wed, 8 May 2024 10:11:35 -0700 Kees Cook wrote:
> > Split this per subsystem, please.
>
> I've done a few painful API transitions before, and I don't think the
> complexity of these changes needs a per-subsystem constification pass. I
> think this series is the right approach, but that patch
On Tue, May 07, 2024 at 12:27:10PM -0700, Allen wrote:
> On Tue, May 7, 2024 at 12:23 PM Russell King (Oracle)
> wrote:
> >
> > On Tue, May 07, 2024 at 07:01:11PM +, Allen Pais wrote:
> > > The only generic interface to execute asynchronously in the BH context is
> > > tasklet; however, it's
On Wed, Apr 24, 2024 at 08:12:34PM -0700, Jakub Kicinski wrote:
> On Tue, 23 Apr 2024 09:54:35 +0200 Thomas Weißschuh wrote:
> > The series was split from my larger series sysctl-const series [0].
> > It only focusses on the proc_handlers but is an important step to be
> > able to move all static
On Wed, May 08, 2024 at 11:54:04AM GMT, Puranjay Mohan wrote:
> The Linux Kernel Memory Model [1][2] requires RMW operations that have a
> return value to be fully ordered.
>
> BPF atomic operations with BPF_FETCH (including BPF_XCHG and
> BPF_CMPXCHG) return a value back so they need to be JITed
arc allmodconfig gcc
arc allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-001-20240508 gcc
arc randconfig
On Fri, 3 May 2024 at 13:26, Michael Ellerman wrote:
>
> With -Wextra clang warns about pointer arithmetic using a null pointer.
> When building with CONFIG_PCI=n, that triggers a warning in the IO
> accessors, eg:
>
> In file included from linux/arch/powerpc/include/asm/io.h:672:
>
On Wed, May 08, 2024 at 11:54:04AM +, Puranjay Mohan wrote:
> The Linux Kernel Memory Model [1][2] requires RMW operations that have a
> return value to be fully ordered.
>
> BPF atomic operations with BPF_FETCH (including BPF_XCHG and
> BPF_CMPXCHG) return a value back so they need to be
Bjorn Helgaas writes:
> From: Bjorn Helgaas
>
> Fix typos, most reported by "codespell arch/powerpc". Only touches
> comments, no code changes.
>
> Signed-off-by: Bjorn Helgaas
> Cc: Nicholas Piggin
> Cc: Christophe Leroy
> Cc: linuxppc-dev@lists.ozlabs.org
Applied to powerpc/next.
[1/1]
On Wed, 8 May 2024 10:55:05 +0200 Erhard Furtner wrote:
> I could do that with the explanation you stated. But should any
> further questions arise in this process I would also lack the
> technical background to deal with them. ;)
Alright, submitted :)
> I also noticed a similar #ifdef
On Mon, 15 Apr 2024 09:27:29 +0530, Vaibhav Jain wrote:
> This reverts commit 180c6b072bf3 ("KVM: PPC: Book3S HV nestedv2: Do not
> cancel pending decrementer exception") [1] which prevented canceling a
> pending HDEC exception for nestedv2 KVM guests. It was done to avoid
> overhead of a
On Tue, 11 Apr 2023 15:44:46 +0930, Joel Stanley wrote:
> The documentation mentions KVM_CAP_PPC_RADIX_MMU, but the defines in the
> kvm headers spell it KVM_CAP_PPC_MMU_RADIX. Similarly with
> KVM_CAP_PPC_MMU_HASH_V3.
>
>
Applied to powerpc/topic/ppc-kvm.
[1/1] KVM: PPC: Fix documentation for
On Sun, 28 Jan 2024 12:34:25 +0100, Christophe JAILLET wrote:
> The return value of kvmppc_gse_put_buff_info() is not assigned to 'rc' and
> 'rc' is uninitialized at this point.
> So the error handling can not work.
>
> Assign the expected value to 'rc' to fix the issue.
>
>
> [...]
Applied to
On Thu, 25 Jan 2024 16:33:48 +0800, Kunwu Chan wrote:
> This part was commented from commit 2f4cf5e42d13 ("Add book3s.c")
> in about 14 years before.
> If there are no plans to enable this part code in the future,
> we can remove this dead code.
>
>
Applied to powerpc/topic/ppc-kvm.
[1/1] KVM:
On Fri, 03 May 2024 17:56:18 +1000, Michael Ellerman wrote:
> With -Wextra clang warns about pointer arithmetic using a null pointer.
> When building with CONFIG_PCI=n, that triggers a warning in the IO
> accessors, eg:
>
> In file included from linux/arch/powerpc/include/asm/io.h:672:
>
On Fri, 03 May 2024 12:10:12 +1000, Stephen Rothwell wrote:
> This list was moved many years ago.
>
>
Applied to powerpc/next.
[1/1] Fix the address of the linuxppc-dev mailing list
https://git.kernel.org/powerpc/c/fae573060c8da4d84a2551c6753d272abfda8ddc
cheers
On Mon, 08 Apr 2024 13:31:08 +0800, Yang Li wrote:
> Fix some function names in kernel-doc comments.
>
>
Applied to powerpc/next.
[2/3] powerpc: Fix kernel-doc comments in fsl_gtm.c
https://git.kernel.org/powerpc/c/97bd2693b399cfd436acaa230d8f09e4c39e8e5c
[3/3] powerpc/rtas: Add
On Mon, 08 Apr 2024 16:39:16 +0800, Yang Li wrote:
> Fix the kernel-doc annotation for the 'skip' parameter in the
> partial_decompress() function by adding a missing underscore and colon.
>
>
Applied to powerpc/next.
[1/3] powerpc: boot: Fix kernel-doc param for partial_decompress
On Wed, 10 Jan 2024 19:42:37 +0530, Naveen N Rao wrote:
> All supported compilers today (gcc v5.1+ and clang v11+) have support for
> -mcmodel=medium. As such, NO_MINIMAL_TOC is no longer being set. Remove
> NO_MINIMAL_TOC as well as the fallback to -mminimal-toc.
>
>
Applied to powerpc/next.
On Wed, 08 May 2024 00:01:50 +1000, Michael Ellerman wrote:
> If both CONFIG_SENSORS_AMS_PMU and CONFIG_SENSORS_AMS_I2C are unset,
> there is an unused variable warning in the ams driver:
>
> drivers/macintosh/ams/ams-core.c: In function 'ams_init':
> drivers/macintosh/ams/ams-core.c:181:29:
On Wed, 24 Jan 2024 11:50:31 +0100, Matthias Schiffer wrote:
> This register number is hardware-specific, rename it for clarity.
>
> FIXME comments are added in a few places where it seems like the wrong
> register is used. As I can't test this, only the rename is done with no
> functional
On Fri, 16 Feb 2024 22:55:17 +0900, Masahiro Yamada wrote:
> Commit ab1a517d55b0 ("powerpc/syscall: Rename syscall_64.c into
> interrupt.c") missed to update these three lines:
>
> GCOV_PROFILE_syscall_64.o := n
> KCOV_INSTRUMENT_syscall_64.o := n
> UBSAN_SANITIZE_syscall_64.o := n
>
>
On Fri, 03 May 2024 01:23:17 +0100, li...@treblig.org wrote:
> The last function to reference module_bug_list went in 2008's
> commit b9754568ef17 ("powerpc: Remove dead module_find_bug code")
> but I don't think that was called since 2006's
> commit 73c9ceab40b1 ("[POWERPC] Generic BUG for
On Thu, 02 May 2024 23:02:04 +0530, Hari Bathini wrote:
> With PCREL addressing, there is no kernel TOC. So, it is not setup in
> prologue when PCREL addressing is used. But the number of instructions
> to skip on a tail call was not adjusted accordingly. That resulted in
> not so obvious failures
On Sat, 13 Jan 2024 08:05:09 +, GUO Zihua wrote:
> The first 32k of memory is reserved for interrupt vectors, however for
> powerpc64 this might not be enough. Fix this by reserving the maximum
> size between 32k and the real size of interrupt vectors.
>
>
Applied to powerpc/next.
[1/1]
On Tue, 09 Mar 2021 19:11:10 +0100, Greg Kurz wrote:
> All these commands end up peeking into the PACA using the user originated
> cpu id as an index. Check the cpu id is valid in order to prevent xmon to
> crash. Instead of printing an error, this follows the same behavior as the
> "lp s #"
On Thu, 28 Dec 2023 15:45:17 +0530, Ghanshyam Agrawal wrote:
> This patch series fixes spelling mistake in the word "auxillary",
> fixes a grammatical error related to full stop and adds the units
> of the size param in the description of eeh_set_pe_aux_size function.
>
> Ghanshyam Agrawal (3):
>
On Fri, 19 Jan 2024 15:38:54 -0500, Frank Li wrote:
> Enable Power Management feature on device tree, including MPC8536,
> MPC8544, MPC8548, MPC8572, P1010, P1020, P1021, P1022, P2020, P2041,
> P3041, T104X, T1024.
>
>
Applied to powerpc/next.
[1/4] powerpc: dts: add power management nodes to
On Wed, 08 May 2024 09:41:17 +0100, Colin Ian King wrote:
> There is a spelling mistake in the help message. Fix it.
>
>
Applied to powerpc/next.
[1/1] selftests/powerpc/dexcr: Fix spelling mistake "predicition" ->
"prediction"
On Tue, 05 Mar 2024 16:36:23 +0100, Christophe Leroy wrote:
> Recent additions in BPF like cpu v4 instructions, test_bpf module
> exhibits the following failures:
>
> test_bpf: #82 ALU_MOVSX | BPF_B jited:1 ret 2 != 1 (0x2 != 0x1)FAIL (1
> times)
> test_bpf: #83 ALU_MOVSX | BPF_H
On Thu, 25 Jan 2024 16:26:37 +0800, Kunwu Chan wrote:
> This part was commented from commit 165785e5c0be ("[POWERPC] Cell
> iommu support") in about 17 years before.
>
> If there are no plans to enable this part code in the future,
> we can remove this dead code.
>
>
> [...]
Applied to
On Fri, 26 Jan 2024 10:12:58 +0800, Kunwu Chan wrote:
> This part was commented from commit a33a7d7309d7
> ("[PATCH] spufs: implement mfc access for PPE-side DMA")
> in about 18 years before.
>
> If there are no plans to enable this part code in the future,
> we can remove this dead code.
>
>
On Fri, 26 Jan 2024 10:50:30 +0800, Kunwu Chan wrote:
> This part was commented in about 19 years before.
> If there are no plans to enable this part code in the future,
> we can remove this dead code.
>
>
Applied to powerpc/next.
[1/1] powerpc/pseries/pci: Code cleanup
On Wed, 17 Apr 2024 21:23:16 +1000, Benjamin Gray wrote:
> Adds support for a process to change its DEXCR value. The implementation is
> somewhat conservative; SBHE (speculative branch hint enable) is not exposed
> as an editable aspect because its effects can bleed over to other threads.
>
> As
On Mon, 25 Mar 2024 16:28:14 +1100, Benjamin Gray wrote:
> patch_instructions() introduces new behaviour with a couple of
> variations. Test each case of
>
> * a repeated 32-bit instruction,
> * a repeated 64-bit instruction (ppc64), and
> * a copied sequence of instructions
>
> [...]
On Mon, 12 Feb 2024 15:50:20 +1100, Benjamin Gray wrote:
> The kasan_init_phys_region() function maps shadow pages necessary for
> the ranges of the linear map backed by physical pages. Currently
> kasan_init_phys_region() is being passed physical addresses, but
> kasan_mem_to_shadow() expects
On 08/05/2024 14.58, Thomas Huth wrote:
On 08/05/2024 14.55, Thomas Huth wrote:
On 08/05/2024 14.27, Nicholas Piggin wrote:
On Wed May 8, 2024 at 1:08 AM AEST, Thomas Huth wrote:
On 04/05/2024 14.28, Nicholas Piggin wrote:
This allows different machines with different requirements to be
While updating the cpus node, commit 40c753993e3a ("powerpc/kexec_file:
Use current CPU info while setting up FDT") first deletes all subnodes
under the /cpus node. However, while adding sub-nodes back, it missed
adding cpus subnodes whose device_type != "cpu", such as l2-cache*,
l3-cache*,
Patch series fixes two kexec issues.
01/02: Update extra size calculation for kexec FDT to avoid kexec load
failure due to FDT_ERR_NOSPACE while including CPU nodes added post
boot and reserved memory ranges.
02/02: Fix update_cpus_node/core_64.c function to include missing device
nodes under
While setting up the FDT for kexec, CPU nodes that are added after the
system boots and reserved memory ranges are incorporated into the
initial_boot_params (base FDT).
However, they are not taken into account when determining the additional
size needed for the kexec FDT. As a result, kexec fails
On Tue, May 07 2024 at 15:23, Vignesh Balasubramanian wrote:
> +struct xfeat_component {
> + u32 xfeat_type;
> + u32 xfeat_sz;
> + u32 xfeat_off;
> + u32 xfeat_flags;
> +} __packed;
Why repeating xfeat_ for all member names?
u32 type;
u32 size;
u32
On 08/05/2024 14.55, Thomas Huth wrote:
On 08/05/2024 14.27, Nicholas Piggin wrote:
On Wed May 8, 2024 at 1:08 AM AEST, Thomas Huth wrote:
On 04/05/2024 14.28, Nicholas Piggin wrote:
This allows different machines with different requirements to be
supported by run_tests.sh, similarly to how
On 08/05/2024 14.27, Nicholas Piggin wrote:
On Wed May 8, 2024 at 1:08 AM AEST, Thomas Huth wrote:
On 04/05/2024 14.28, Nicholas Piggin wrote:
This allows different machines with different requirements to be
supported by run_tests.sh, similarly to how different accelerators
are handled.
Gautam Menghani writes:
> PAPR hypervisor has introduced three new counters in the VPA area of
> LPAR CPUs for KVM L2 guest (see [1] for terminology) observability - 2
> for context switches from host to guest and vice versa, and 1 counter
> for getting the total time spent inside the KVM guest.
On Wed May 8, 2024 at 1:08 AM AEST, Thomas Huth wrote:
> On 04/05/2024 14.28, Nicholas Piggin wrote:
> > This allows different machines with different requirements to be
> > supported by run_tests.sh, similarly to how different accelerators
> > are handled.
> >
> > Acked-by: Thomas Huth
> >
On Tue May 7, 2024 at 12:56 AM AEST, Gautam Menghani wrote:
> PAPR hypervisor has introduced three new counters in the VPA area of
> LPAR CPUs for KVM L2 guest (see [1] for terminology) observability - 2
> for context switches from host to guest and vice versa, and 1 counter
> for getting the
On 5/8/2024 10:00 AM, Hans Verkuil wrote:
On 06/05/2024 10:49, Shengjiu Wang wrote:
On Fri, May 3, 2024 at 4:42 PM Mauro Carvalho Chehab wrote:
Em Fri, 3 May 2024 10:47:19 +0900
Mark Brown escreveu:
On Thu, May 02, 2024 at 10:26:43AM +0100, Mauro Carvalho Chehab wrote:
Mauro Carvalho
The Linux Kernel Memory Model [1][2] requires RMW operations that have a
return value to be fully ordered.
BPF atomic operations with BPF_FETCH (including BPF_XCHG and
BPF_CMPXCHG) return a value back so they need to be JITed to fully
ordered operations. POWERPC currently emits relaxed operations
On Fri, May 03, 2024 at 04:09:40PM +0200, Thomas Weißschuh wrote:
> Hey Joel,
>
...
> > # Motivation
> > As I read it, the motivation for these constification efforts are:
> > 1. It provides increased safety: Having things in .rodata section reduces
> > the
> >attack surface. This is
Michael Ellerman writes:
> Puranjay Mohan writes:
>> The Linux Kernel Memory Model [1][2] requires RMW operations that have a
>> return value to be fully ordered.
>>
>> BPF atomic operations with BPF_FETCH (including BPF_XCHG and
>> BPF_CMPXCHG) return a value back so they need to be JITed to
Kees
Could you comment on the feasibility of this alternative from the
Control Flow Integrity perspective. My proposal is to change the
proc_handler to void* and back in the same release. So there would not
be a kernel released with a void* proc_handler.
> > However, there is an alternative way
On Mon, 6 May 2024 18:10:20 -0700
Jakub Kicinski wrote:
> Excellent! Do you want to submit that as an official patch?
> The explanation is that we can't call disable_irq() from atomic
> context (which which netpoll runs). But the callback is no longer
> necessary as we can depend on NAPI to do
There is a spelling mistake in the help message. Fix it.
Signed-off-by: Colin Ian King
---
tools/testing/selftests/powerpc/dexcr/chdexcr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/powerpc/dexcr/chdexcr.c
On Tue, May 07, 2024 at 03:23:31PM +0530, Vignesh Balasubramanian wrote:
> Add a new .note section containing type, size, offset and flags of
> every xfeature that is present.
>
> This information will be used by the debuggers to understand the XSAVE
> layout of the machine where the core file is
On 06/05/2024 10:49, Shengjiu Wang wrote:
> On Fri, May 3, 2024 at 4:42 PM Mauro Carvalho Chehab
> wrote:
>>
>> Em Fri, 3 May 2024 10:47:19 +0900
>> Mark Brown escreveu:
>>
>>> On Thu, May 02, 2024 at 10:26:43AM +0100, Mauro Carvalho Chehab wrote:
Mauro Carvalho Chehab escreveu:
>>>
>
62 matches
Mail list logo
