On Sun, Mar 02, 2025 at 04:20:02PM +0800, Kuan-Wei Chiu wrote: > Hi Yury, > > On Sat, Mar 01, 2025 at 10:10:20PM -0500, Yury Norov wrote: > > On Sat, Mar 01, 2025 at 10:23:52PM +0800, Kuan-Wei Chiu wrote: > > > Add generic C implementations of __paritysi2(), __paritydi2(), and > > > __parityti2() as fallback functions in lib/parity.c. These functions > > > compute the parity of a given integer using a bitwise approach and are > > > marked with __weak, allowing architecture-specific implementations to > > > override them. > > > > > > This patch serves as preparation for using __builtin_parity() by > > > ensuring a fallback mechanism is available when the compiler does not > > > inline the __builtin_parity(). > > > > > > Co-developed-by: Yu-Chun Lin <eleanor15x@xxxxxxxxx> > > > Signed-off-by: Yu-Chun Lin <eleanor15x@xxxxxxxxx> > > > Signed-off-by: Kuan-Wei Chiu <visitorckw@xxxxxxxxx> > > > --- > > > lib/Makefile | 2 +- > > > lib/parity.c | 48 ++++++++++++++++++++++++++++++++++++++++++++++++ > > > 2 files changed, 49 insertions(+), 1 deletion(-) > > > create mode 100644 lib/parity.c > > > > > > diff --git a/lib/Makefile b/lib/Makefile > > > index 7bab71e59019..45affad85ee4 100644 > > > --- a/lib/Makefile > > > +++ b/lib/Makefile > > > @@ -51,7 +51,7 @@ obj-y += bcd.o sort.o parser.o debug_locks.o random32.o \ > > > bsearch.o find_bit.o llist.o lwq.o memweight.o kfifo.o \ > > > percpu-refcount.o rhashtable.o base64.o \ > > > once.o refcount.o rcuref.o usercopy.o errseq.o bucket_locks.o \ > > > - generic-radix-tree.o bitmap-str.o > > > + generic-radix-tree.o bitmap-str.o parity.o > > > obj-y += string_helpers.o > > > obj-y += hexdump.o > > > obj-$(CONFIG_TEST_HEXDUMP) += test_hexdump.o > > > diff --git a/lib/parity.c b/lib/parity.c > > > new file mode 100644 > > > index 000000000000..a83ff8d96778 > > > --- /dev/null > > > +++ b/lib/parity.c > > > @@ -0,0 +1,48 @@ > > > +// SPDX-License-Identifier: GPL-2.0-only > > > +/* > > > + * lib/parity.c > > > + * > > > + * Copyright (C) 2025 Kuan-Wei Chiu <visitorckw@xxxxxxxxx> > > > + * Copyright (C) 2025 Yu-Chun Lin <eleanor15x@xxxxxxxxx> > > > + * > > > + * __parity[sdt]i2 can be overridden by linking arch-specific versions. > > > + */ > > > + > > > +#include <linux/export.h> > > > +#include <linux/kernel.h> > > > + > > > +/* > > > + * One explanation of this algorithm: > > > + * https://funloop.org/codex/problem/parity/README.html > > > > I already asked you not to spread this link. Is there any reason to > > ignore it? > > > In v2, this algorithm was removed from bitops.h, so I moved the link > here instead. I'm sorry if it seemed like I ignored your comment. Yes, it is. > In v1, I used the same approach as parity8() because I couldn't justify > the performance impact in a specific driver or subsystem. However, > multiple people commented on using __builtin_parity or an x86 assembly > implementation. I'm not ignoring their feedback-I want to address these Please ask those multiple people: are they ready to maintain all that zoo of macros, weak implementations, arch implementations and stubs for no clear benefit? Performance is always worth it, but again I see not even a hint that the drivers care about performance. You don't measure it, so don't care as well. Right? > comments. Before submitting, I sent an email explaining my current > approach: using David's suggested method along with __builtin_parity, > but no one responded. So, I decided to submit v2 for discussion > instead. For discussion use tag RFC. > > To avoid mistakes in v3, I want to confirm the following changes before > sending it: > > (a) Change the return type from int to bool. > (b) Avoid __builtin_parity and use the same approach as parity8(). > (c) Implement parity16/32/64() as single-line inline functions that > call the next smaller variant after xor. > (d) Add a parity() macro that selects the appropriate parityXX() based > on type size. > (e) Update users to use this parity() macro. > > However, (d) may require a patch affecting multiple subsystems at once > since some places that already include bitops.h have functions named > parity(), causing conflicts. Unless we decide not to add this macro in > the end. > > As for checkpatch.pl warnings, they are mostly pre-existing coding > style issues in this series. I've kept them as-is, but if preferred, > I'm fine with fixing them. Checkpatch only complains on new lines. Particularly this patch should trigger checkpatch warning because it adds a new file but doesn't touch MAINTAINERS. > If anything is incorrect or if there are concerns, please let me know. > > Regards, > Kuan-Wei > > diff --git a/include/linux/bitops.h b/include/linux/bitops.h > index c1cb53cf2f0f..47b7eca8d3b7 100644 > --- a/include/linux/bitops.h > +++ b/include/linux/bitops.h > @@ -260,6 +260,43 @@ static inline int parity8(u8 val) > return (0x6996 >> (val & 0xf)) & 1; > } > > +static inline bool parity16(u16 val) > +{ > + return parity8(val ^ (val >> 8)); > +} > + > +static inline bool parity32(u32 val) > +{ > + return parity16(val ^ (val >> 16)); > +} > + > +static inline bool parity64(u64 val) > +{ > + return parity32(val ^ (val >> 32)); > +} That was discussed between Jiri and me in v2. Fixed types functions are needed only in a few very specific cases. With the exception of I3C driver (which doesn't look good for both Jiri and me), all the drivers have the type of variable passed to the parityXX() matching the actual variable length. It means that fixed-type versions of the parity() are simply not needed. So if we don't need them, please don't introduce it. > +#define parity(val) \ > +({ \ > + bool __ret; \ > + switch (BITS_PER_TYPE(val)) { \ > + case 64: \ > + __ret = parity64(val); \ > + break; \ > + case 32: \ > + __ret = parity32(val); \ > + break; \ > + case 16: \ > + __ret = parity16(val); \ > + break; \ > + case 8: \ > + __ret = parity8(val); \ > + break; \ > + default: \ > + BUILD_BUG(); \ > + } \ > + __ret; \ > +}) > + > /** > * __ffs64 - find first set bit in a 64 bit word > * @word: The 64 bit word
