[GIT PULL] Please pull powerpc/linux.git powerpc-6.13-1 tag

2024-11-22 Thread Michael Ellerman
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Linus, Please pull powerpc updates for 6.13. There's a fixup required after the merge in our ftrace code: diff --git a/arch/powerpc/include/asm/ftrace.h b/arch/powerpc/include/asm/ftrace.h index bb2c90997618..db481b336bca 100644 - --- a/arch/p

Re: [PATCH] powerpc: Transliterate author name and remove FIXME

2024-11-22 Thread Michael Ellerman
Thorsten Blum writes: > On 11. Nov 2024, at 02:11, Michael Ellerman wrote: >> Thorsten Blum writes: >>> The name is Mimi Phuong-Thao Vo. >> >> Is that the correct spelling? >> >> The github commit below suggests it's Mimi Phûông-Thåo Võ. >> >> And presumably the author preferred that spelling,

[PATCH v10 5/5] rust: Use gendwarfksyms + extended modversions for CONFIG_MODVERSIONS

2024-11-22 Thread Matthew Maurer
From: Sami Tolvanen Previously, two things stopped Rust from using MODVERSIONS: 1. Rust symbols are occasionally too long to be represented in the original versions table 2. Rust types cannot be properly hashed by the existing genksyms approach because: * Looking up type definitions

[PATCH v10 2/5] modpost: Produce extended MODVERSIONS information

2024-11-22 Thread Matthew Maurer
Generate both the existing modversions format and the new extended one when running modpost. Presence of this metadata in the final .ko is guarded by CONFIG_EXTENDED_MODVERSIONS. We no longer generate an error on long symbols in modpost if CONFIG_EXTENDED_MODVERSIONS is set, as they can now be app

[PATCH v10 4/5] Documentation/kbuild: Document storage of symbol information

2024-11-22 Thread Matthew Maurer
Document where exported and imported symbols are kept, format options, and limitations. Signed-off-by: Matthew Maurer --- Documentation/kbuild/modules.rst | 20 1 file changed, 20 insertions(+) diff --git a/Documentation/kbuild/modules.rst b/Documentation/kbuild/modules.rst

[PATCH v10 3/5] modules: Allow extended modversions without basic MODVERSIONS

2024-11-22 Thread Matthew Maurer
If you know that your kernel modules will only ever be loaded by a newer kernel, you can disable BASIC_MODVERSIONS to save space. This also allows easy creation of test modules to seee how tooling will respond to modules that only have the new format. Signed-off-by: Matthew Maurer --- kernel/mod

[PATCH v10 0/5] Extended MODVERSIONS Support

2024-11-22 Thread Matthew Maurer
This patch series is intended for use alongside the Implement DWARF modversions series [1] to enable RUST and MODVERSIONS at the same time. Elsewhere, we've seen a desire for long symbol name support for LTO symbol names [2], and the previous series came up [3] as a possible solution rather than h

[PATCH v10 1/5] modules: Support extended MODVERSIONS info

2024-11-22 Thread Matthew Maurer
Adds a new format for MODVERSIONS which stores each field in a separate ELF section. This initially adds support for variable length names, but could later be used to add additional fields to MODVERSIONS in a backwards compatible way if needed. Any new fields will be ignored by old user tooling, un

Re: [PATCH v9 3/5] modules: Allow extended modversions without basic MODVERSIONS

2024-11-22 Thread Matthew Maurer
> > depends on !COMPILE_TEST > > + selects BASIC_MODVERSIONS > > tested? 'selects' is not valid. > Apologies. Tested before making BASIC_MODVERSIONS default. I've fixed this locally, and will re-test with the whole stack before resending.

Re: [PATCH v9 3/5] modules: Allow extended modversions without basic MODVERSIONS

2024-11-22 Thread Randy Dunlap
On 11/22/24 4:19 PM, Matthew Maurer wrote: > If you know that your kernel modules will only ever be loaded by a newer > kernel, you can disable BASIC_MODVERSIONS to save space. This also > allows easy creation of test modules to seee how tooling will respond to > modules that only have the new f

[PATCH v9 3/5] modules: Allow extended modversions without basic MODVERSIONS

2024-11-22 Thread Matthew Maurer
If you know that your kernel modules will only ever be loaded by a newer kernel, you can disable BASIC_MODVERSIONS to save space. This also allows easy creation of test modules to seee how tooling will respond to modules that only have the new format. Signed-off-by: Matthew Maurer --- kernel/mod

[PATCH v9 5/5] rust: Use gendwarfksyms + extended modversions for CONFIG_MODVERSIONS

2024-11-22 Thread Matthew Maurer
From: Sami Tolvanen Previously, two things stopped Rust from using MODVERSIONS: 1. Rust symbols are occasionally too long to be represented in the original versions table 2. Rust types cannot be properly hashed by the existing genksyms approach because: * Looking up type definitions

[PATCH v9 4/5] Documentation/kbuild: Document storage of symbol information

2024-11-22 Thread Matthew Maurer
Document where exported and imported symbols are kept, format options, and limitations. Signed-off-by: Matthew Maurer --- Documentation/kbuild/modules.rst | 20 1 file changed, 20 insertions(+) diff --git a/Documentation/kbuild/modules.rst b/Documentation/kbuild/modules.rst

[PATCH v9 2/5] modpost: Produce extended MODVERSIONS information

2024-11-22 Thread Matthew Maurer
Generate both the existing modversions format and the new extended one when running modpost. Presence of this metadata in the final .ko is guarded by CONFIG_EXTENDED_MODVERSIONS. We no longer generate an error on long symbols in modpost if CONFIG_EXTENDED_MODVERSIONS is set, as they can now be app

[PATCH v9 0/5] Extended MODVERSIONS Support

2024-11-22 Thread Matthew Maurer
This patch series is intended for use alongside the Implement DWARF modversions series [1] to enable RUST and MODVERSIONS at the same time. Elsewhere, we've seen a desire for long symbol name support for LTO symbol names [2], and the previous series came up [3] as a possible solution rather than h

[PATCH v9 1/5] modules: Support extended MODVERSIONS info

2024-11-22 Thread Matthew Maurer
Adds a new format for MODVERSIONS which stores each field in a separate ELF section. This initially adds support for variable length names, but could later be used to add additional fields to MODVERSIONS in a backwards compatible way if needed. Any new fields will be ignored by old user tooling, un

Re: [PATCH v3 2/6] x86/uaccess: Avoid barrier_nospec() in 64-bit __get_user()

2024-11-22 Thread Linus Torvalds
On Fri, 22 Nov 2024 at 11:13, Linus Torvalds wrote: > > I've only compiled it so far, about to actually boot into it. Looks fine. Sent out a proper patch with commit message etc at https://lore.kernel.org/all/20241122193305.7316-1-torva...@linux-foundation.org/ because it looks good to me.

Re: [PATCH v3 2/6] x86/uaccess: Avoid barrier_nospec() in 64-bit __get_user()

2024-11-22 Thread Linus Torvalds
On Thu, 21 Nov 2024 at 19:57, Linus Torvalds wrote: > > Anyway, that was a long way of saying: I really think we should just > special-case the (few) important cases that get reported. Because any > *big* improvements will come not from just inlining. Looking around at the futex code some more, I

Re: [RFC PATCH 01/10] powerpc/chrp: Remove CHRP support

2024-11-22 Thread Segher Boessenkool
On Thu, Nov 21, 2024 at 09:41:36AM +0100, John Paul Adrian Glaubitz wrote: > >> Pegasos2 users still exist, but admittedly they mainly use MorphOS and > >> AmigaOS4 on these machines. > > > > The Linux CHRP support is still present in v6.12, which will be an LTS > > for the next 2 years at least, s

Re: [PATCH v3 2/6] x86/uaccess: Avoid barrier_nospec() in 64-bit __get_user()

2024-11-22 Thread Linus Torvalds
On Fri, 22 Nov 2024 at 01:20, Christophe Leroy wrote: > > On powerpc for this kind of stuff I have been using do { } while (0); > with a break; in the middle, see for instance __put_user() or > __get_user_size_allowed() in arch/powerpc/include/asm/uaccess.h Oh, that's indeed a nicer syntax. I'll

Re: [PATCH v3 10/25] pci/p2pdma: Don't initialise page refcount to one

2024-11-22 Thread Bjorn Helgaas
On Fri, Nov 22, 2024 at 12:40:31PM +1100, Alistair Popple wrote: > The reference counts for ZONE_DEVICE private pages should be > initialised by the driver when the page is actually allocated by the > driver allocator, not when they are first created. This is currently > the case for MEMORY_DEVICE_

Re: [PATCH] powerpc: Transliterate author name and remove FIXME

2024-11-22 Thread Thorsten Blum
On 11. Nov 2024, at 02:11, Michael Ellerman wrote: > Thorsten Blum writes: >> The name is Mimi Phuong-Thao Vo. > > Is that the correct spelling? > > The github commit below suggests it's Mimi Phûông-Thåo Võ. > > And presumably the author preferred that spelling, otherwise they would > have just

RE: [PATCH v3 2/6] x86/uaccess: Avoid barrier_nospec() in 64-bit __get_user()

2024-11-22 Thread David Laight
From: Linus Torvalds > Sent: 21 November 2024 22:16 > > On Thu, 21 Nov 2024 at 13:40, Josh Poimboeuf wrote: > > > > The profile is showing futex_get_value_locked(): > > Ahh. > > > That has several callers, so we can probably just use get_user() there? > > Yeah, that's the simplest thing. That

Re: [PATCH v3 2/6] x86/uaccess: Avoid barrier_nospec() in 64-bit __get_user()

2024-11-22 Thread Christophe Leroy
Le 22/11/2024 à 04:57, Linus Torvalds a écrit : I'm not loving the "if (0)" with the labels inside of it. But it's the only way I can see to make a statement expression like this work, since you can't have a "return" inside of it. On powerpc for this kind of stuff I have been using do { }