book3s_64_vio currently accounts for pinned pages with
account_locked_vm() which charges the pages to mm->locked_vm. To make
this consistent with other drivers switch to using
vm_account_pinned().
Signed-off-by: Alistair Popple
Cc: Michael Ellerman
Cc: Nicholas Piggin
Cc: Christophe Leroy
Cc:
Convert from accounting pages against locked_vm to accounting them to
pinned_vm. This allows struct vm_account to be used to track the
mm_struct used to charge the pages. A future change also uses this to
track a cgroup for controlling pinned pages.
Signed-off-by: Alistair Popple
Cc: Michael Elle
Kernel drivers that pin pages should account these pages against
either user->locked_vm and/or mm->pinned_vm and fail the pinning if
RLIMIT_MEMLOCK is exceeded and CAP_IPC_LOCK isn't held.
Currently drivers open-code this accounting and use various methods to
update the atomic variables and check
On 03/02/23 02:31, Eric DeVolder wrote:
On 2/2/23 09:37, Eric DeVolder wrote:
On 2/1/23 00:38, Sourabh Jain wrote:
On architectures like PowerPC the crash notes are available for all
possible CPUs. So let's populate the elfcorehdr for all possible
CPUs having crash notes to avoid updating
On 02/02/23 21:07, Eric DeVolder wrote:
On 2/1/23 00:38, Sourabh Jain wrote:
On architectures like PowerPC the crash notes are available for all
possible CPUs. So let's populate the elfcorehdr for all possible
CPUs having crash notes to avoid updating elfcorehdr during in-kernel
crash update
On 02/02/23 21:07, Eric DeVolder wrote:
On 2/1/23 00:38, Sourabh Jain wrote:
On architectures like PowerPC the crash notes are available for all
possible CPUs. So let's populate the elfcorehdr for all possible
CPUs having crash notes to avoid updating elfcorehdr during in-kernel
crash update
> On 02-Feb-2023, at 10:14 PM, Kajol Jain wrote:
>
> Testcase stat_all_metrics.sh fails in powerpc:
>
> 92: perf all metrics test : FAILED!
>
> Logs with verbose:
>
> [command]# ./perf test 92 -vv
> 92: perf all metrics test :
> --- start ---
> test
The RFI and STF security mitigation options can flip the
interrupt_exit_not_reentrant static branch condition concurrently with
the interrupt exit code which tests that branch.
Interrupt exit tests this condition to set MSR[EE|RI] for exit, then
again in the case a soft-masked interrupt is found p
> On 02-Feb-2023, at 6:27 AM, Arnaldo Carvalho de Melo wrote:
>
> Em Tue, Jan 31, 2023 at 07:20:01PM +0530, Athira Rajeev escreveu:
>> "bpf" tests fails in environment with missing libtraceevent
>> support as below:
>>
>> # ./perf test 36
>> 36: BPF filter
On Sat, Feb 4, 2023 at 10:29 AM Josh Poimboeuf wrote:
>
> On Sat, Feb 04, 2023 at 09:12:31AM +0800, Guo Ren wrote:
> > On Sat, Feb 4, 2023 at 6:05 AM Josh Poimboeuf wrote:
> > >
> > > arch_cpu_idle_dead() doesn't return. Make that more explicit with a
> > > BUG().
> > >
> > > BUG() is preferable
Enable HAVE_ARCH_KCSAN on all powerpc platforms, permitting use of the
kernel concurrency sanitiser through the CONFIG_KCSAN_* kconfig options.
KCSAN requires compiler builtins __atomic_* 64-bit values, and so only
report support on PPC64.
See documentation in Documentation/dev-tools/kcsan.rst for
In order for KCSAN to increase its likelihood of observing a data race,
it sets a watchpoint on memory accesses and stalls, allowing for
detection of conflicting accesses by other kernel threads or interrupts.
Stalls are implemented by injecting a call to udelay in instrumented code.
To prevent re
Instrumented memory accesses provided by KCSAN will access core-local
memories (which will save and restore IRQs) as well as restoring IRQs
directly. Avoid recursive instrumentation by applying __no_kcsan
annotation to IRQ restore routines.
Signed-off-by: Rohan McLure
---
arch/powerpc/kernel/irq
Add Kernel Concurrency Sanitiser support for PPC64. Doing so involves
exclusion of a number of compilation units from instrumentation, as was
done with KASAN.
KCSAN uses watchpoints on memory accesses to enforce the semantics of
the Linux kernel memory model, notifying the user of observed data ra
Annotate memory barriers *mb() with calls to kcsan_mb(), signaling to
compilers supporting KCSAN that the respective memory barrier has been
issued. Rename memory barrier *mb() to __*mb() to opt in for
asm-generic/barrier.h to generate the respective *mb() macro.
Signed-off-by: Rohan McLure
---
v
Exclude various incompatible compilation units from KCSAN
instrumentation.
Signed-off-by: Rohan McLure
---
arch/powerpc/kernel/Makefile | 10 ++
arch/powerpc/kernel/trace/Makefile | 1 +
arch/powerpc/kernel/vdso/Makefile | 1 +
arch/powerpc/lib/Makefile | 2 ++
arch/po
On Sun, Feb 05, 2023 at 11:46:12AM +1100, Michael Ellerman wrote:
> Josh Poimboeuf writes:
> > On Tue, Jan 24, 2023 at 07:38:03PM -0800, Josh Poimboeuf wrote:
> >> Fix a livepatch bug seen when reloading a patched module.
> >>
> >> This is the powerpc counterpart to Song Liu's fix for a similar i
Attempt to handle cases such as with a downstream port of the ASMedia
ASM2824 PCIe switch where link training never completes and the link
continues switching between speeds indefinitely with the data link layer
never reaching the active state.
It has been observed with a downstream port of the
Determine whether Data Link Layer Link Active Reporting is available
ahead of calling any fixups so that the cached value can be used there
and later on.
Signed-off-by: Maciej W. Rozycki
---
New change in v6.
---
drivers/pci/probe.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
Hi,
This is v6 of the change to work around a PCIe link training phenomenon
where a pair of devices both capable of operating at a link speed above
2.5GT/s seems unable to negotiate the link speed and continues training
indefinitely with the Link Training bit switching on and off repeatedly
a
Use `link_active_reporting' to determine whether Data Link Layer Link
Active Reporting is available rather than re-retrieving the capability.
Signed-off-by: Maciej W. Rozycki
---
NB this has been compile-tested only with PPC64LE and x86-64
configurations.
New change in v6.
---
drivers/pci/hotp
Use `link_active_reporting' to determine whether Data Link Layer Link
Active Reporting is available rather than re-retrieving the capability.
Signed-off-by: Maciej W. Rozycki
---
NB this has been compile-tested only with PPC64LE and x86-64
configurations.
New change in v6.
---
drivers/net/eth
Use `link_active_reporting' to determine whether Data Link Layer Link
Active Reporting is available rather than re-retrieving the capability.
Signed-off-by: Maciej W. Rozycki
---
NB this has been compile-tested only with a PPC64LE configuration.
New change in v6.
---
arch/powerpc/kernel/eeh_pe
Make `quirk_enable_clear_retrain_link' `pci_fixup_early' so that any later
fixups can rely on `clear_retrain_link' to have been already initialised.
Signed-off-by: Maciej W. Rozycki
---
No change from v5.
New change in v5.
---
drivers/pci/quirks.c |6 +++---
1 file changed, 3 insertions(+)
Rename LINK_RETRAIN_TIMEOUT to PCIE_LINK_RETRAIN_TIMEOUT and make it
available via "pci.h" for PCI drivers to use.
Signed-off-by: Maciej W. Rozycki
---
No change from v5.
New change in v5.
---
drivers/pci/pci.h |2 ++
drivers/pci/pcie/aspm.c |4 +---
2 files changed, 3 insertions(
> On 03-Feb-2023, at 3:55 PM, Nicholas Piggin wrote:
>
> On Fri Feb 3, 2023 at 4:26 PM AEST, Sachin Sant wrote:
>> I am observing an intermittent crash while running powerpc/security
>> selftests on a Power10 LPAR booted with powerpc/merge branch code.
>>
>> [ cut here ]--
On 04/02/23 22:52, Randy Dunlap wrote:
kexec (PPC64) code calls memory_hotplug_max(). Add the header declaration
for it from . Using does not work since
the #include for depends on CONFIG_NUMA=y, which is not
set in this kernel config file.
I didn't realize that linux/mmzone.h includes asm/
rhel-8.3
x86_64 rhel-8.3-func
x86_64rhel-8.3-kselftests
clang tested configs:
riscvrandconfig-r042-20230205
s390 randconfig-r044-20230205
hexagon randconfig-r045-20230205
hexagon randconfig
defconfig
x86_64 allyesconfig
x86_64 rhel-8.3
clang tested configs:
riscvrandconfig-r042-20230205
s390 randconfig-r044-20230205
hexagon randconfig-r045-20230205
hexagon randconfig
On Tue, 31 Jan 2023 08:36:15 +0530, Sourabh Jain wrote:
> On Systems where online memory is lesser compared to max memory, the
> kexec_file_load system call may fail to load the kdump kernel with the
> below errors:
>
> "Failed to update fdt with linux,drconf-usable-memory property"
> "Err
On Sat, 28 Jan 2023 18:11:58 +0530, Sathvika Vasireddy wrote:
> Objtool throws the following warning:
> arch/powerpc/kvm/booke.o: warning: objtool: kvmppc_fill_pt_regs+0x30:
> unannotated intra-function call
>
> Fix this warning by allowing the function to set the value of 'nip' field
> using _TH
On Sat, 21 Jan 2023 20:01:56 +1000, Nicholas Piggin wrote:
> Interrupt entry sets the soft mask to IRQS_ALL_DISABLED to match the
> hard irq disabled state. So when should_hard_irq_enable() returns true
> because we want PMI interrupts in irq handlers, MSR[EE] is enabled but
> PMIs just get soft-ma
On Sat, 21 Jan 2023 19:53:52 +1000, Nicholas Piggin wrote:
> When PMI interrupts are soft-masked, local_irq_save() will clear the PMI
> mask bit, allowing PMIs in and causing a race condition. This causes a
> deadlock in native_hpte_insert via hash_preload, which depends on PMIs
> being disabled si
On Sat, 28 Jan 2023 18:11:38 +0530, Sathvika Vasireddy wrote:
> Objtool throws the following warning:
> arch/powerpc/kernel/head_85xx.o: warning: objtool: .head.text+0x1a6c:
> unannotated intra-function call
>
> Fix this warning by annotating KernelSPE symbol with SYM_FUNC_START_LOCAL
> and SYM_FU
On Mon, 30 Jan 2023 12:47:07 +1100, Michael Ellerman wrote:
> In kexec_extra_fdt_size_ppc64() there's logic to estimate how much
> extra space will be needed in the device tree for some memory related
> properties.
>
> That logic uses the size of RAM divided by drmem_lmb_size() to do the
> estimat
On Mon, 30 Jan 2023 12:44:01 +1100, Michael Ellerman wrote:
> The recent commit 76d588dddc45 ("powerpc/imc-pmu: Fix use of mutex in
> IRQs disabled section") fixed warnings (and possible deadlocks) in the
> IMC PMU driver by converting the locking to use spinlocks.
>
> It also converted the init-t
On Tue, 31 Jan 2023 22:14:07 +1100, Michael Ellerman wrote:
> Commit baf1ed24b27d ("powerpc/mm: Remove empty hash__ functions")
> removed some empty hash MMU flushing routines, but got a bit overeager
> and also removed the call to hash__tlb_flush() from tlb_flush().
>
> In regular use this doesn'
On Tue, 10 Jan 2023 23:47:52 +1100, Michael Ellerman wrote:
> If a relocatable kernel is loaded at an address that is not 2MB aligned
> and told not to relocate to zero, the kernel can crash due to
> mark_rodata_ro() incorrectly changing some read-write data to read-only.
>
> Scenarios where the m
38 matches
Mail list logo
