[RFC PATCH 3/3] Remove HAVE_VIRT_CPU_ACCOUNTING_GEN option

This option was created in commit 554b0004d0ec4 ("vtime: Add HAVE_VIRT_CPU_ACCOUNTING_GEN Kconfig") for architectures to indicate they support the 64-bit cputime_t required for VIRT_CPU_ACCOUNTING_GEN. The cputime_t type has since been removed, so this doesn't have any meaning. Remove it. Cc: lin

[RFC PATCH 2/3] powerpc: remove the last remnants of cputime_t

cputime_t is no longer, converted to u64. Signed-off-by: Nicholas Piggin --- arch/powerpc/include/asm/cputime.h | 17 + arch/powerpc/kernel/time.c | 23 ++- 2 files changed, 3 insertions(+), 37 deletions(-) diff --git a/arch/powerpc/include/asm/cputim

[RFC PATCH 1/3] powerpc/32: Implement HAVE_CONTEXT_TRACKING_USER support

Context tracking involves tracking user, kernel, guest switches. This enables existing context tracking code for interrupt entry on 32-bit. KVM and interrupt exit already has context tracking calls. Signed-off-by: Nicholas Piggin --- arch/powerpc/Kconfig | 2 +- arch/powerpc/inc

[RFC PATCH 0/3] powerpc/32: nohz full support

Doesn't seem to be much more involved in adding context tracking and generic virt cpu accounting support for 32-bit, which is all that's left to support NO_HZ_FULL. I tested this with e5500 SMP kernel with isolated and nohz CPU, and it seems to be doing the right thing -- periodic tick is stopped

[PATCH 2/2] powerpc/64: Fix msr_check_and_set/clear MSR[EE] race

irq soft-masking means that when Linux irqs are disabled, the MSR[EE] value can change from 1 to 0 asynchronously: if a masked interrupt of the PACA_IRQ_MUST_HARD_MASK variety fires while irqs are disabled, the masked handler will return with MSR[EE]=0. This means a sequence like mtmsr(mfmsr() | M

[PATCH 1/2] powerpc/64s/interrupt: Change must-hard-mask interrupt check from BUG to WARN

This new assertion added is generally harmless and gets fixed up naturally, but it does indicate a problem with MSR manipulation somewhere. Fixes: c39fb71a54f0 ("powerpc/64s/interrupt: masked handler debug check for previous hard disable") Reported-by: Sachin Sant Signed-off-by: Nicholas Piggin

Re: [RFC PATCH 2/2] powerpc: nop trap instruction after WARN_ONCE fires

On Sat Sep 24, 2022 at 2:47 AM AEST, Christophe Leroy wrote: > > > Le 23/09/2022 à 17:41, Nicholas Piggin a écrit : > > WARN_ONCE and similar are often used in frequently executed code, and > > should not crash the system. The program check interrupt caused by > > WARN_ON_ONCE can be a significant

Re: [PATCH v2] i2c-pasemi: PASemi I2C controller IRQ enablement

"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

linux-next: manual merge of the powerpc tree with the kbuild tree

Hi all, Today's linux-next merge of the powerpc tree got a conflict in: arch/powerpc/Makefile between commit: ce697ccee1a8 ("kbuild: remove head-y syntax") from the kbuild tree and commit: dfc3095cec27 ("powerpc: Remove CONFIG_FSL_BOOKE") from the powerpc tree. I fixed it up (I used t

linux-next: manual merge of the powerpc tree with the kbuild tree

Hi all, Today's linux-next merge of the powerpc tree got a conflict in: arch/powerpc/kernel/Makefile between commit: 321648455061 ("kbuild: use obj-y instead extra-y for objects placed at the head") from the kbuild tree and commit: dfc3095cec27 ("powerpc: Remove CONFIG_FSL_BOOKE") fro

Re: [PATCH] tools/perf: Fix aggr_printout to display cpu field irrespective of core value

On Mon, Oct 3, 2022 at 7:03 AM atrajeev wrote: > > On 2022-10-02 05:17, Ian Rogers wrote: > > On Thu, Sep 29, 2022 at 5:56 AM James Clark > > wrote: > >> > >> > >> > >> On 29/09/2022 09:49, Athira Rajeev wrote: > >> > > >> > > >> >> On 28-Sep-2022, at 9:05 PM, James Clark wrote: > >> >> > >> >>

Re: [PATCH net-next v6 1/9] dt-bindings: net: Expand pcs-handle to an array

On Fri, 30 Sep 2022 16:09:25 -0400, Sean Anderson wrote: > This allows multiple phandles to be specified for pcs-handle, such as > when multiple PCSs are present for a single MAC. To differentiate > between them, also add a pcs-handle-names property. > > Signed-off-by: Sean Anderson > --- > This

Re: [PATCH v6 4/8] phy: fsl: Add Lynx 10G SerDes driver

Hi Vinod/Ioana, Ioana, last time you commented [1], you said you were interested in testing this out on some other SoCs. Did you ever end up doing that? I've you've had a chance to look at this driver more closely, do you have any suggestions for dynamic reconfiguration? [1] https://lore.kernel.

Re: [PATCH v3 1/7] ASoC: dt-bindings: fsl_rpmsg: Add a property to assign the rpmsg channel

On Fri, 30 Sep 2022 14:44:35 +0800, Chancel Liu wrote: > Add a string property to assign the rpmsg channel this sound card sits > on. This property can be omitted if there is only one sound card and it > sits on "rpmsg-audio-channel". > > Signed-off-by: Chancel Liu > --- > .../devicetree/binding

[PATCH] powerpc: Implement slightly better 64-bit LE non-VMX memory copy

From: Paul Mackerras At present, on 64-bit little-endian machines, we have the choice of either a dumb loop that does one byte per iteration, or an optimized loop using VMX instructions. On microwatt, we don't have VMX, so we are stuck with the dumb loop, which is very slow. This makes the dumb

[PATCH 5.19 002/101] tools/perf: Fix out of bound access to cpu mask array

From: Athira Rajeev [ Upstream commit cbd7bfc7fd99acdde58ec2b0bce990158fba1654 ] The cpu mask init code in "record__mmap_cpu_mask_init" function access "bits" array part of "struct mmap_cpu_mask". The size of this array is the value from cpu__max_cpu().cpu. This array is used to contain the cp