On Tue 13. Aug 2024 0:32:37 CEST, Kolbjørn Barmen wrote:
Ever since 6.10, my macmini G4 behaved unstable when dealing with lots of
I/O activity, such as sync'ing of Gentoo portage tree, unpacking kernel
source tarball, building large software packages (or kernel) etc.
After a bit of testing, and
Hello Baoquan,
On 13/08/24 10:34, Baoquan He wrote:
On 08/12/24 at 09:46am, Sourabh Jain wrote:
..
---
Changelog:
Since v1:
https://lore.kernel.org/all/20240805050829.297171-1-sourabhj...@linux.ibm.com/
- Update crash_hotplug sysfs document as suggested by Petr T
- Update an error
On Tue, 13 Aug 2024 09:32:07 +1000 Stephen Rothwell
wrote:
> Hi all,
>
> The following commit is also in the mm-hotfixes tree as a different commit
> (but the same patch):
>
> e7a9af8c93aa ("powerpc/mm: Fix size of allocated PGDIR")
>
> This is commit
>
> 6cd04a440f57 ("powerpc/mm: fix s
cc-12
i386 allnoconfig clang-18
i386 allnoconfig gcc-12
i386 allyesconfig clang-18
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20240812 clang-18
i386 buildonly-randconfig-001-20240813 g
allnoconfig clang-18
i386 allnoconfig gcc-12
i386 allyesconfig clang-18
i386 allyesconfig gcc-12
i386 buildonly-randconfig-001-20240812 clang-18
i386 buildonly-randconfig-001
Hi all,
The following commit is also in the mm-hotfixes tree as a different commit
(but the same patch):
e7a9af8c93aa ("powerpc/mm: Fix size of allocated PGDIR")
This is commit
6cd04a440f57 ("powerpc/mm: fix size of allocated PGDIR")
in the mm-hot-fixes-unstable branch of the mm-hotfixes t
Ever since 6.10, my macmini G4 behaved unstable when dealing with lots of
I/O activity, such as sync'ing of Gentoo portage tree, unpacking kernel
source tarball, building large software packages (or kernel) etc.
After a bit of testing, and patient kernel rebuilding (while crashing) I
found the c
On Sun, 11 Aug 2024 17:35:07 +0200, Krzysztof Kozlowski wrote:
> Drop the RCPM consumer example from the binding (LPUART device node),
> because:
> 1. Using phandles is typical syntax, thus explaining it is not needed in
>the provider binding,
> 2. It has 'fsl,rcpm-wakeup' property which is n
* Michael Ellerman [240812 04:26]:
> Add an optional close() callback to struct vm_special_mapping. It will
> be used, by powerpc at least, to handle unmapping of the VDSO.
>
> Although support for unmapping the VDSO was initially added
> for CRIU[1], it is not desirable to guard that support beh
On Fri, Aug 09, 2024 at 11:15:37PM +0200, Erhard Furtner wrote:
> Greetings!
>
> When KASAN is enabled the Overflow KUnit test fails:
>
> [...]
> ok 16 shift_nonsense_test
> # overflow_allocation_test: 11 allocation overflow tests finished
> ===
This is only relevant to the two archs that support PUD dax, aka, x86_64
and ppc64. PUD THPs do not yet exist elsewhere, and hugetlb PUDs do not
count in this case.
DAX have had PUD mappings for years, but change protection path never
worked. When the path is triggered in any form (a simple test
Some new helpers will be needed for pud entry updates soon. Introduce
these helpers by referencing the pmd ones. Namely:
- pudp_invalidate(): this helper invalidates a huge pud before a split
happens, so that the invalidated pud entry will make sure no race will
happen (either with softwar
Introduce arch_check_zapped_pud() to sanity check shadow stack on PUD zaps.
It has the same logic as the PMD helper.
One thing to mention is, it might be a good idea to use page_table_check in
the future for trapping wrong setups of shadow stack pgtable entries [1].
That is left for the future as
When working on mprotect() on 1G dax entries, I hit an zap bad pud
error when zapping a huge pud that is with PROT_NONE permission.
Here the problem is x86's pud_leaf() requires both PRESENT and PSE bits
set to report a pud entry as a leaf, but that doesn't look right, as
it's not following the pX
Some new helpers will be needed for pud entry updates soon. Introduce
these helpers by referencing the pmd ones. Namely:
- pudp_invalidate(): this helper invalidates a huge pud before a split
happens, so that the invalidated pud entry will make sure no race will
happen (either with softwar
mprotect() does mmu notifiers in PMD levels. It's there since 2014 of
commit a5338093bfb4 ("mm: move mmu notifier call from change_protection to
change_pmd_range").
At that time, the issue was that NUMA balancing can be applied on a huge
range of VM memory, even if nothing was populated. The not
Currently the dax fault handler dumps the vma range when dynamic debugging
enabled. That's mostly not useful. Dump the (aligned) address instead
with the order info.
Acked-by: David Hildenbrand
Signed-off-by: Peter Xu
---
drivers/dax/device.c | 6 +++---
1 file changed, 3 insertions(+), 3 del
[Based on mm-unstable, commit 98808d08fc0f, Aug 7th. NOTE: it is
intentional to not have rebased to latest mm-unstable, as this is to
replace the queued v4]
v5 Changelog:
- Rename patch subject "mm/x86: arch_check_zapped_pud()", add "Implement" [tglx]
- Mostly rewrote commit messages for the x86
On Mon, Aug 12, 2024 at 12:50:35PM -0400, Frank Li wrote:
> Convert binding doc newwork.txt to yaml format.
>
> HDLC part:
> - Convert to "fsl,ucc-hdlc.yaml".
> - Add missed reg and interrupt property.
> - Update example to pass build.
>
> ethernet part:
> - Convert to net/fsl,cpm-enet.yaml
> - Add
Convert binding doc newwork.txt to yaml format.
HDLC part:
- Convert to "fsl,ucc-hdlc.yaml".
- Add missed reg and interrupt property.
- Update example to pass build.
ethernet part:
- Convert to net/fsl,cpm-enet.yaml
- Add 0x in example, which should be hex value
- Add ref to ethernet-controller.y
On Sun, Aug 11, 2024 at 05:35:07PM +0200, Krzysztof Kozlowski wrote:
> Drop the RCPM consumer example from the binding (LPUART device node),
> because:
> 1. Using phandles is typical syntax, thus explaining it is not needed in
>the provider binding,
> 2. It has 'fsl,rcpm-wakeup' property which
On Mon, Aug 12, 2024 at 04:19:13PM GMT, Stephen Rothwell wrote:
> > For the subscribers, to see how to manage you subscription, you will be
> > able to end an email to for
> > instructions. Hopefully you all won't find it too restrictive.
> >
> > Please report any problems with the list after th
On 8/12/24 15:31, Jaroslav Kysela wrote:
> On 12. 08. 24 12:24, Shengjiu Wang wrote:
>> On Fri, Aug 9, 2024 at 10:01 PM Jaroslav Kysela wrote:
>>>
>>> On 09. 08. 24 14:52, Pierre-Louis Bossart wrote:
>>>
> And metadata
> ioctl can be called many times which can meet the ratio modifier
>
On 12. 08. 24 12:24, Shengjiu Wang wrote:
On Fri, Aug 9, 2024 at 10:01 PM Jaroslav Kysela wrote:
On 09. 08. 24 14:52, Pierre-Louis Bossart wrote:
And metadata
ioctl can be called many times which can meet the ratio modifier
requirement (ratio may be drift on the fly)
Interesting, that's ye
On Sun, 04 Aug 2024 13:20:31 +0200, Uwe Kleine-König wrote:
> This driver doesn't use the driver_data member of struct i2c_device_id,
> so don't explicitly initialize this member.
>
> This prepares putting driver_data in an anonymous union which requires
> either no initialization or named designa
On Wed, 31 Jul 2024 15:06:13 +0200, Thomas Zimmermann wrote:
> Commit a1cacb8a8e70 ("backlight: Add BACKLIGHT_POWER_ constants for
> power states") introduced dedicated constants for backlight power states.
> Convert PowerPC code to the new constants.
>
> The new constants replace the fbdev consta
On Wed, 07 Aug 2024 10:56:04 +0800, Jinjie Ruan wrote:
> commit 0db880fc865f ("powerpc: Avoid nmi_enter/nmi_exit in real mode
> interrupt.") has a config comment typo, and the #if/#else/#endif section
> is small and doesn't nest additional #ifdefs so the comment is useless
> and should be removed c
On Wed, 31 Jul 2024 13:12:47 -0600, Rob Herring (Arm) wrote:
> Use of_property_present() to test for property presence rather than
> of_get_property(). This is part of a larger effort to remove callers
> of of_get_property() and similar functions. of_get_property() leaks
> the DT property data poin
On Wed, 29 May 2024 00:11:23 +0100, li...@treblig.org wrote:
> 'cgr_comp' has been unused since
> commit 96f413f47677 ("soc/fsl/qbman: fix issue in
> qman_delete_cgr_safe()").
>
> Remove it.
>
>
> [...]
Applied to powerpc/fixes.
[1/1] soc/fsl/qbman: remove unused struct 'cgr_comp'
https:
On Thu, 08 Aug 2024 11:32:47 +0200, Christophe Leroy wrote:
> Commit 6b0e82791bd0 ("powerpc/e500: switch to 64 bits PGD on 85xx
> (32 bits)") increased the size of PGD entries but failed to increase
> the PGD directory.
>
> Use the size of pgd_t instead of the size of pointers to calculate
> the a
On Thu, 08 Aug 2024 09:05:08 +0200, Christophe Leroy wrote:
> Booting with CONFIG_DEBUG_VIRTUAL leads to following warning when
> passing hugepage reservation on command line:
>
> Kernel command line: hugepagesz=1g hugepages=1 hugepagesz=64m hugepages=1
> hugepagesz=256m hugepages=1 noreboot
>
On Sun, Aug 11, 2024 at 10:09:35AM +0300, Baruch Siach wrote:
> From: Catalin Marinas
>
> Hardware DMA limit might not be power of 2. When RAM range starts above
> 0, say 4GB, DMA limit of 30 bits should end at 5GB. A single high bit
> can not encode this limit.
>
> Use plain address for DMA zon
On Fri, Aug 9, 2024 at 10:01 PM Jaroslav Kysela wrote:
>
> On 09. 08. 24 14:52, Pierre-Louis Bossart wrote:
>
> >> And metadata
> >> ioctl can be called many times which can meet the ratio modifier
> >> requirement (ratio may be drift on the fly)
> >
> > Interesting, that's yet another way of hand
Currently exec-target.c file is linked as static and this
post a requirement to install libc dev package to build.
Without it, build-break when compiling selftest/powerpc/benchmark.
CC exec_target
/usr/bin/ld: cannot find -lc: No such file or directory
collect2: error: ld returned 1 exit s
Linus noticed that the error handling in __arch_setup_additional_pages()
fails to clear the mm VDSO pointer if _install_special_mapping()
fails. In practice there should be no actual bug, because if there's an
error the VDSO pointer is cleared later in arch_setup_additional_pages().
However it's n
Now that powerpc no longer uses arch_unmap() to handle VDSO unmapping,
there are no meaningful implementions left. Drop support for it
entirely, and update comments which refer to it.
Suggested-by: Linus Torvalds
Signed-off-by: Michael Ellerman
Acked-by: David Hildenbrand
Reviewed-by: Thomas Gl
Add a close() callback to the VDSO special mapping to handle unmapping
of the VDSO. That will make it possible to remove the arch_unmap() hook
entirely in a subsequent patch.
Suggested-by: Linus Torvalds
Signed-off-by: Michael Ellerman
Reviewed-by: David Hildenbrand
---
arch/powerpc/include/as
Add an optional close() callback to struct vm_special_mapping. It will
be used, by powerpc at least, to handle unmapping of the VDSO.
Although support for unmapping the VDSO was initially added
for CRIU[1], it is not desirable to guard that support behind
CONFIG_CHECKPOINT_RESTORE.
There are othe
David Hildenbrand writes:
> On 07.08.24 14:41, Michael Ellerman wrote:
>> Add an optional close() callback to struct vm_special_mapping. It will
>> be used, by powerpc at least, to handle unmapping of the VDSO.
>>
>> Suggested-by: Linus Torvalds
>> Signed-off-by: Michael Ellerman
>> ---
>> in
"Liam R. Howlett" writes:
> * Michael Ellerman [240807 08:41]:
>> Add an optional close() callback to struct vm_special_mapping. It will
>> be used, by powerpc at least, to handle unmapping of the VDSO.
>>
>> Suggested-by: Linus Torvalds
>> Signed-off-by: Michael Ellerman
>> ---
>> include/li
An iommu domain is allocated in portal_set_cpu() and is attached to
pcfg->dev in the same function.
Use iommu_paging_domain_alloc() to make it explicit.
Signed-off-by: Lu Baolu
Reviewed-by: Jason Gunthorpe
Link: https://lore.kernel.org/r/2024061008.88197-14-baolu...@linux.intel.com
---
dri
41 matches
Mail list logo
