On 23/02/24 1:05 pm, Sourabh Jain wrote:
Hello Hari,
Hi Sourabh,
Build failure detected.
Thanks for trying out the patches.
On 13/02/24 17:01, Hari Bathini wrote:
Remove CONFIG_CRASH_DUMP dependency on CONFIG_KEXEC. CONFIG_KEXEC_CORE
was used at places where CONFIG_CRASH_DUMP or
Currnetly, With a single event queue EEH recovery is entirely
serialized and takes place within a single kernel thread. This
can cause recovery to take a long time when there are many
devices.
Have the recovery event queue per PHB and allow the recovery to
happen independently from other PHBs.
This change is based on Sam Bobroff's patches which aimed
to allow recovery to happen in parallel between PHBs and PEs,
Due to various reasons the patches did not get in.
But having parallel recovery between PHBs is fairly simple and
gives significant improvement on powervm, Since powervm
On Wed, 07 Feb 2024 13:52:18 +1000, Nicholas Piggin wrote:
> When a new ibm,pa/pi-features bit is introduced that is intended to
> apply to existing systems and features, it may have an "inverted"
> meaning (i.e., bit clear => feature available; bit set => unavailable).
> Depending on the nature
On Wed, 27 Dec 2023 17:24:02 +1000, Nicholas Piggin wrote:
> This (hopefully) fixes the ELFv2 bug that Geoff reported, with patch
> 1. And a couple of other possible improvements I noticed.
>
> I don't have a PS3 setup[*] so I have only compile tested these, I'm
> sorry.
>
> [*] Is RPCS3 usable
On Wed, 21 Feb 2024 16:40:14 +0100, Uwe Kleine-König wrote:
> this series converts all platform drivers below drivers/powerpc to
> struct platform_driver::remove_new(). See commit 5c5a7680e67b
> ("platform: Provide a remove callback that returns no value") for an
> extended explanation and the
On Fri, 19 Jan 2024 10:27:51 +, Geoff Levand wrote:
> The following changes since commit 44a1aad2fe6c10bfe0589d8047057b10a4c18a19:
>
> Merge branch 'topic/ppc-kvm' into next (2023-12-29 15:30:45 +1100)
>
> are available in the Git repository at:
>
>
When the watchdog determines that the current soft lockup is due
to an interrupt storm based on CPU utilization, reporting the
most frequent interrupts could be good enough for further
troubleshooting.
Below is an example of interrupt storm. The call tree does not
provide useful information, but
We could use the irq_desc::tot_count member to avoid the summation
loop for interrupts which are not marked as 'PER_CPU' interrupts in
'show_interrupts'. This could reduce the time overhead of reading
/proc/interrupts.
Originally-by: Thomas Gleixner
Signed-off-by: Bitao Hu
---
The soft lockup detector lacks a mechanism to identify interrupt storms
as root cause of a lockup. To enable this the detector needs a
mechanism to snapshot the interrupt count statistics on a CPU when the
detector observes a potential lockup scenario and compare that against
the interrupt count
The following softlockup is caused by interrupt storm, but it cannot be
identified from the call tree. Because the call tree is just a snapshot
and doesn't fully capture the behavior of the CPU during the soft lockup.
watchdog: BUG: soft lockup - CPU#28 stuck for 23s! [fio:83921]
...
Call
Hi, guys.
I have implemented a low-overhead method for detecting interrupt
storm in softlockup. Please review it, all comments are welcome.
Changes from v9 to v10:
- The two patches related to 'watchdog/softlockup' remain unchanged.
- The majority of the work related to 'genirq' is contributed
allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-001-20240225 gcc
arc randconfig-002-20240225 gcc
arm
Mimi, James, Jarkko, David,
you remained silent for a whole release cycle.
Is there anything we can do to get this forward?
Thanks,
//richard
Am Dienstag, 13. Februar 2024, 10:59:56 CET schrieb Richard Weinberger:
> Am Montag, 5. Februar 2024, 09:39:07 CET schrieb David Gstir:
> > Hi,
> >
> >
When running `make -C powerpc/pmu run_tests` from top level selftests
directory, currently this error is being reported
make: Entering directory '/home/maddy/linux/tools/testing/selftests/powerpc/pmu'
Makefile:40: warning: overriding recipe for target 'emit_tests'
../../lib.mk:111: warning:
While running ftrace specific kernel selftests following warning
is seen on a Power10 logical partition (LPAR) booted with
latest mainline kernel.
[ cut here ]
precision 63492 too large
WARNING: CPU: 15 PID: 2538829 at lib/vsprintf.c:2721 set_precision+0x68/0xa4
Modules
arc allnoconfig gcc
arc allyesconfig gcc
arc axs103_smp_defconfig gcc
arc defconfig gcc
arc randconfig-001-20240225 gcc
arc
gcc
arc allnoconfig gcc
arc allyesconfig gcc
arc axs103_smp_defconfig gcc
arc defconfig gcc
arc randconfig-001-20240225 gcc
arc
allnoconfig gcc
arc allyesconfig gcc
arc defconfig gcc
arc randconfig-001-20240225 gcc
arc randconfig-002-20240225 gcc
arm allmodconfig gcc
arm
19 matches
Mail list logo
