Re: [GIT PULL] sysctl constification changes for v6.11-rc1
Hello: This pull request was applied to riscv/linux.git (for-next) by Linus Torvalds : On Wed, 24 Jul 2024 23:00:14 +0200 you wrote: > Linus > > Constifying ctl_table structs will prevent the modification of > proc_handler function pointers as they would reside in .rodata. To get > there, the proc_handler arguments must first be const qualified which > requires this (fairly large) treewide PR. Sending it in the tail end of > of the merge window after a suggestion from Kees to avoid unneeded merge > conflicts. It has been rebased on top of > 7a3fad30fd8b4b5e370906b3c554f64026f56c2f. > I can send it later if it makes more sense on your side; please tell me > what you prefer. > > [...] Here is the summary with links: - [GIT,PULL] sysctl constification changes for v6.11-rc1 https://git.kernel.org/riscv/c/b485625078ca You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [GIT PULL] sysctl constification changes for v6.11-rc1
Hello: This pull request was applied to riscv/linux.git (fixes) by Linus Torvalds : On Wed, 24 Jul 2024 23:00:14 +0200 you wrote: > Linus > > Constifying ctl_table structs will prevent the modification of > proc_handler function pointers as they would reside in .rodata. To get > there, the proc_handler arguments must first be const qualified which > requires this (fairly large) treewide PR. Sending it in the tail end of > of the merge window after a suggestion from Kees to avoid unneeded merge > conflicts. It has been rebased on top of > 7a3fad30fd8b4b5e370906b3c554f64026f56c2f. > I can send it later if it makes more sense on your side; please tell me > what you prefer. > > [...] Here is the summary with links: - [GIT,PULL] sysctl constification changes for v6.11-rc1 https://git.kernel.org/riscv/c/f8a8b94d0698 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH] riscv, kexec: fix the ifdeffery for AFLAGS_kexec_relocate.o
Hello:
This patch was applied to riscv/linux.git (fixes)
by Andrew Morton :
On Fri, 1 Dec 2023 14:25:38 +0800 you wrote:
> This was introduced in commit fba8a8674f68 ("RISC-V: Add kexec
> support").
>
> It should work on CONFIG_KEXEC_CORE, but not CONFIG_KEXEC only, since
> we could set CONFIG_KEXEC_FILE=y and CONFIG_KEXEC=N, or only set
> CONFIG_CRASH_DUMP=y and disable both CONFIG_KEXEC and CONFIG_KEXEC_FILE.
> In these cases, the AFLAGS won't take effect with the current ifdeffery
> for AFLAGS_kexec_relocate.o.
>
> [...]
Here is the summary with links:
- riscv, kexec: fix the ifdeffery for AFLAGS_kexec_relocate.o
https://git.kernel.org/riscv/c/d53a154cdc54
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v4 0/7] kexec_file: print out debugging message if required
Hello: This series was applied to riscv/linux.git (fixes) by Andrew Morton : On Wed, 13 Dec 2023 13:57:40 +0800 you wrote: > Currently, specifying '-d' on kexec command will print a lot of debugging > informationabout kexec/kdump loading with kexec_load interface. > > However, kexec_file_load prints nothing even though '-d' is specified. > It's very inconvenient to debug or analyze the kexec/kdump loading when > something wrong happened with kexec/kdump itself or develper want to > check the kexec/kdump loading. > > [...] Here is the summary with links: - [v4,1/7] kexec_file: add kexec_file flag to control debug printing (no matching commit) - [v4,2/7] kexec_file: print out debugging message if required (no matching commit) - [v4,3/7] kexec_file, x86: print out debugging message if required (no matching commit) - [v4,4/7] kexec_file, arm64: print out debugging message if required (no matching commit) - [v4,5/7] kexec_file, ricv: print out debugging message if required https://git.kernel.org/riscv/c/eb7622d908a0 - [v4,6/7] kexec_file, power: print out debugging message if required (no matching commit) - [v4,7/7] kexec_file, parisc: print out debugging message if required (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v2 1/2] resource: add walk_system_ram_res_rev()
Hello:
This patch was applied to riscv/linux.git (fixes)
by Andrew Morton :
On Wed, 15 Nov 2023 21:00:27 +0800 you wrote:
> This function, being a variant of walk_system_ram_res() introduced in
> commit 8c86e70acead ("resource: provide new functions to walk through
> resources"), walks through a list of all the resources of System RAM
> in reversed order, i.e., from higher to lower.
>
> It will be used in kexec_file code to load kernel, initrd etc when
> preparing kexec reboot.
>
> [...]
Here is the summary with links:
- [v2,1/2] resource: add walk_system_ram_res_rev()
https://git.kernel.org/riscv/c/7acf164b259d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH 1/2] riscv, crash: don't export some symbols when CONFIG_MMU=n
Hello: This series was applied to riscv/linux.git (fixes) by Andrew Morton : On Mon, 4 Dec 2023 10:19:36 +0800 you wrote: > When dropping select of KEXEC and dependency on ARCH_SUPPORTS_KEXEC > from CRASH_DUMP, compiling error is reported when below config items are > set: > --- > CONFIG_CRASH_CORE=y > CONFIG_KEXEC_CORE=y > CONFIG_CRASH_DUMP=y > .. > > [...] Here is the summary with links: - [1/2] riscv, crash: don't export some symbols when CONFIG_MMU=n https://git.kernel.org/riscv/c/c41bd2514184 - [2/2] riscv, kexec: fix dependency of two items (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH 0/2] kexec_file: Load kernel at top of system RAM if required
Hello: This series was applied to riscv/linux.git (fixes) by Andrew Morton : On Tue, 14 Nov 2023 17:16:56 +0800 you wrote: > Justification: > == > Kexec_load interface has been doing top down searching and loading > kernel/initrd/purgtory etc to prepare for kexec reboot. In that way, > the benefits are that it avoids to consume and fragment limited low > memory which satisfy DMA buffer allocation and big chunk of continuous > memory during system init; and avoids to stir with BIOS/FW reserved > or occupied areas, or corner case handling/work around/quirk occupied > areas when doing system init. By the way, the top-down searching and > loading of kexec-ed kernel is done in user space utility code. > > [...] Here is the summary with links: - [1/2] resource: add walk_system_ram_res_rev() (no matching commit) - [2/2] kexec_file: Load kernel at top of system RAM if required https://git.kernel.org/riscv/c/b3ba234171cd You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH V1 0/3] riscv: kexec: cleanup and fixups
Hello: This series was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Thu, 7 Sep 2023 18:33:01 +0800 you wrote: > Hi, > > I had posted 2 patches [1][2] for riscv/kexec, but there was no "effective" > response to them until now, so I merged them in this series with the 3rd > fixup. > > Anyway, this series contains a cleanup for riscv_kexec_relocate() and two > fixups > for KEXEC_FILE and had passed the basic kexec test in my 64bit Qemu-virt. > > [...] Here is the summary with links: - [V1,1/3] riscv: kexec: Cleanup riscv_kexec_relocate (no matching commit) - [V1,2/3] riscv: kexec: Align the kexeced kernel entry https://git.kernel.org/riscv/c/1bfb2b618d52 - [V1,3/3] riscv: kexec: Remove -fPIE for PURGATORY_CFLAGS (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH -next v9 0/2] support allocating crashkernel above 4G explicitly on riscv
Hello: This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Wed, 26 Jul 2023 17:49:58 + you wrote: > On riscv, the current crash kernel allocation logic is trying to > allocate within 32bit addressible memory region by default, if > failed, try to allocate without 4G restriction. > > In need of saving DMA zone memory while allocating a relatively large > crash kernel region, allocating the reserved memory top down in > high memory, without overlapping the DMA zone, is a mature solution. > Hence this patchset introduces the parameter option crashkernel=X,[high,low]. > > [...] Here is the summary with links: - [-next,v9,1/2] riscv: kdump: Implement crashkernel=X,[high,low] https://git.kernel.org/riscv/c/5882e5acf18d - [-next,v9,2/2] docs: kdump: Update the crashkernel description for riscv https://git.kernel.org/riscv/c/33f0dd973d4e You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [RESEND PATCH -fixes 1/2] riscv: Export va_kernel_pa_offset in vmcoreinfo
Hello:
This series was applied to riscv/linux.git (fixes)
by Palmer Dabbelt :
On Mon, 24 Jul 2023 18:09:16 +0800 you wrote:
> Since RISC-V Linux v6.4, the commit 3335068f8721 ("riscv: Use
> PUD/P4D/PGD pages for the linear mapping") changes phys_ram_base
> from the physical start of the kernel to the actual start of the DRAM.
>
> The Crash-utility's VTOP() still uses phys_ram_base and kernel_map.virt_addr
> to translate kernel virtual address, that failed the Crash with Linux v6.4
> [1].
>
> [...]
Here is the summary with links:
- [RESEND,-fixes,1/2] riscv: Export va_kernel_pa_offset in vmcoreinfo
https://git.kernel.org/riscv/c/fbe7d19d2b7f
- [RESEND,-fixes,2/2] Documentation: kdump: Add va_kernel_pa_offset for
RISCV64
https://git.kernel.org/riscv/c/640c503d7dbd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
___
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH v2 0/3] RISC-V: Fix a few kexec_file_load(2) failures
Hello: This series was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Wed, 26 Jul 2023 11:53:58 +0200 you wrote: > From: Petr Tesarik > > The kexec_file_load(2) syscall does not work at least in some kernel > builds. For details see the relevant section in this blog post: > > https://sigillatum.tesarici.cz/2023-07-21-state-of-riscv64-kdump.html > > [...] Here is the summary with links: - [v2,1/3] riscv/kexec: handle R_RISCV_CALL_PLT relocation type https://git.kernel.org/riscv/c/1be0b05b3a80 - [v2,2/3] riscv/purgatory: do not link with string.o and its dependencies (no matching commit) - [v2,3/3] riscv/kexec: load initrd high in available memory https://git.kernel.org/riscv/c/0ccd2e803745 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH 1/2] RISC-V: kexec: Fix memory leak of fdt buffer
Hello: This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Fri, 4 Nov 2022 17:56:57 +0800 you wrote: > This is reported by kmemleak detector: > > unreferenced object 0xff6082864000 (size 9588): > comm "kexec", pid 146, jiffies 4294900634 (age 64.788s) > hex dump (first 32 bytes): > d0 0d fe ed 00 00 12 ed 00 00 00 48 00 00 11 40 ...H...@ > 00 00 00 28 00 00 00 11 00 00 00 02 00 00 00 00 ...( > backtrace: > [] kmemleak_alloc+0x34/0x3e > [ ] kmalloc_order+0x9c/0xc4 > [ ] kmalloc_order_trace+0x34/0xb6 > [ ] __kmalloc+0x5c2/0x62a > [<2bd497b2>] kvmalloc_node+0x66/0xd6 > [<906542fa>] of_kexec_alloc_and_setup_fdt+0xa6/0x6ea > [ ] elf_kexec_load+0x206/0x4ec > [<36548e09>] kexec_image_load_default+0x40/0x4c > [<79fbe1b4>] sys_kexec_file_load+0x1c4/0x322 > [<40c62c03>] ret_from_syscall+0x0/0x2 > > [...] Here is the summary with links: - [1/2] RISC-V: kexec: Fix memory leak of fdt buffer https://git.kernel.org/riscv/c/96df59b1ae23 - [2/2] RISC-V: kexec: Fix memory leak of elf header buffer https://git.kernel.org/riscv/c/cbc32023ddbd You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
Re: [PATCH V5 0/2] Support VMCOREINFO export for RISCV64
Hello: This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Wed, 26 Oct 2022 22:42:06 +0800 you wrote: > As disscussed in below patch set, the patch of 'describe VMCOREINFO export in > Documentation' > need to update according to Bagas's comments. > https://lore.kernel.org/linux-riscv/22aaf52e-8cc8-4d11-99cb-88de4d113...@kernel.org/ > > As others patches in above patch set already applied, so this patch set only > contains below two > patches. > > [...] Here is the summary with links: - [V5,1/2] RISC-V: Add arch_crash_save_vmcoreinfo support https://git.kernel.org/riscv/c/649d6b1019a2 - [V5,2/2] Documentation: kdump: describe VMCOREINFO export for RISCV64 https://git.kernel.org/riscv/c/c5b4216929eb You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html ___ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec
