Re: [RESEND PATCH] powerpc64/bpf: fix JIT code size calculation of bpf trampoline

Hi Naveen, Thanks for the review. On 03/04/25 9:15 pm, Naveen N Rao wrote: On Wed, Mar 26, 2025 at 08:04:22PM +0530, Hari Bathini wrote: The JIT compile of ldimm instructions can be anywhere between 1-5 instructions long depending on the value being loaded. arch_bpf_trampoline_size() provides

Re: [PATCH 0/9] Remove per-architecture ChaCha skcipher glue code

Eric Biggers wrote: > Currently each architecture exposes ChaCha not only through the library > API, but also through the crypto_skcipher API. That requires each > architecture to implement essentially the same skcipher glue code. > > Following the example of what's been done for crc32 and crc32

Re: [PATCH] tools/lib/perf: Fix -Werror=alloc-size-larger-than in cpumap.c

On Sun, Apr 06, 2025 at 10:04:12PM +0530, Likhitha Korrapati wrote: > perf build break observed when using gcc 13-3 (FC39 ppc64le) > with the following error. > > cpumap.c: In function 'perf_cpu_map__merge': > cpumap.c:414:20: error: argument 1 range [18446744069414584320, > 18446744073709551614]

[PATCH V2 2/3] mm/ptdump: Split effective_prot() into level specific callbacks

Last argument in effective_prot() is u64 assuming pxd_val() returned value (all page table levels) is 64 bit. pxd_val() is very platform specific and its type should not be assumed in generic MM. Split effective_prot() into individual page table level specific callbacks which accepts corresponding

[PATCH V2 3/3] arm64/mm: Define ptdesc_t

Define ptdesc_t type which describes the basic page table descriptor layout on arm64 platform. Subsequently all level specific pxxval_t descriptors are derived from ptdesc_t thus establishing a common original format, which can also be appropriate for page table entries, masks and protection values

[PATCH V2 1/3] mm/ptdump: Split note_page() into level specific callbacks

Last argument passed down in note_page() is u64 assuming pxd_val() returned value (all page table levels) is 64 bit - which might not be the case going ahead when D128 page tables is enabled on arm64 platform. Besides pxd_val() is very platform specific and its type should not be assumed in generic

[PATCH V2 0/3] mm/ptdump: Drop assumption that pxd_val() is u64

Last argument passed down in note_page() is u64 assuming pxd_val() returned value (all page table levels) is 64 bit - which might not be the case going ahead when D128 page tables is enabled on arm64 platform. Besides pxd_val() is very platform specific and its type should not be assumed in generic

[PATCH] ASoC: imx-card: Adjust over allocation of memory in imx_card_parse_of()

Incorrect types are used as sizeof() arguments in devm_kcalloc(). It should be sizeof(dai_link_data) for link_data instead of sizeof(snd_soc_dai_link). This is found by our static analysis tool. Signed-off-by: Chenyuan Yang --- sound/soc/fsl/imx-card.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH] tools/lib/perf: Fix -Werror=alloc-size-larger-than in cpumap.c

> On 6 Apr 2025, at 10:04 PM, Likhitha Korrapati wrote: > > perf build break observed when using gcc 13-3 (FC39 ppc64le) > with the following error. > > cpumap.c: In function 'perf_cpu_map__merge': > cpumap.c:414:20: error: argument 1 range [18446744069414584320, > 18446744073709551614] exce

[PATCH] tools/lib/perf: Fix -Werror=alloc-size-larger-than in cpumap.c

perf build break observed when using gcc 13-3 (FC39 ppc64le) with the following error. cpumap.c: In function 'perf_cpu_map__merge': cpumap.c:414:20: error: argument 1 range [18446744069414584320, 18446744073709551614] exceeds maximum object size 9223372036854775807 [-Werror=alloc-size-larger-tha