Re: [PATCH 00/11] Bump the minimum supported version of LLVM to 13.0.1
Hello: This series was applied to riscv/linux.git (fixes) by Andrew Morton : On Thu, 25 Jan 2024 15:55:06 -0700 you wrote: > Hi all, > > This series bumps the minimum supported version of LLVM for building the > kernel to 13.0.1. The first patch does the bump and all subsequent > patches clean up all the various workarounds and checks for earlier > versions. > > [...] Here is the summary with links: - [07/11] riscv: Remove MCOUNT_NAME workaround https://git.kernel.org/riscv/c/de5f3984664e - [08/11] riscv: Kconfig: Remove version dependency from CONFIG_CLANG_SUPPORTS_DYNAMIC_FTRACE https://git.kernel.org/riscv/c/a38d97181271 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH v3 00/15] mm/memory: optimize fork() with PTE-mapped THP
Hello: This series was applied to riscv/linux.git (fixes) by Andrew Morton : On Mon, 29 Jan 2024 13:46:34 +0100 you wrote: > Now that the rmap overhaul[1] is upstream that provides a clean interface > for rmap batching, let's implement PTE batching during fork when processing > PTE-mapped THPs. > > This series is partially based on Ryan's previous work[2] to implement > cont-pte support on arm64, but its a complete rewrite based on [1] to > optimize all architectures independent of any such PTE bits, and to > use the new rmap batching functions that simplify the code and prepare > for further rmap accounting changes. > > [...] Here is the summary with links: - [v3,01/15] arm64/mm: Make set_ptes() robust when OAs cross 48-bit boundary (no matching commit) - [v3,02/15] arm/pgtable: define PFN_PTE_SHIFT (no matching commit) - [v3,03/15] nios2/pgtable: define PFN_PTE_SHIFT (no matching commit) - [v3,04/15] powerpc/pgtable: define PFN_PTE_SHIFT (no matching commit) - [v3,05/15] riscv/pgtable: define PFN_PTE_SHIFT https://git.kernel.org/riscv/c/57c254b2fb31 - [v3,06/15] s390/pgtable: define PFN_PTE_SHIFT (no matching commit) - [v3,07/15] sparc/pgtable: define PFN_PTE_SHIFT (no matching commit) - [v3,08/15] mm/pgtable: make pte_next_pfn() independent of set_ptes() (no matching commit) - [v3,09/15] arm/mm: use pte_next_pfn() in set_ptes() (no matching commit) - [v3,10/15] powerpc/mm: use pte_next_pfn() in set_ptes() (no matching commit) - [v3,11/15] mm/memory: factor out copying the actual PTE in copy_present_pte() (no matching commit) - [v3,12/15] mm/memory: pass PTE to copy_present_pte() (no matching commit) - [v3,13/15] mm/memory: optimize fork() with PTE-mapped THP (no matching commit) - [v3,14/15] mm/memory: ignore dirty/accessed/soft-dirty bits in folio_pte_batch() (no matching commit) - [v3,15/15] mm/memory: ignore writable bit in folio_pte_batch() (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH 1/1] arch/arm/mm: fix major fault accounting when retrying under per-VMA lock
Hello:
This patch was applied to riscv/linux.git (fixes)
by Andrew Morton :
On Mon, 22 Jan 2024 22:43:05 -0800 you wrote:
> The change [1] missed ARM architecture when fixing major fault accounting
> for page fault retry under per-VMA lock. Add missing code to fix ARM
> architecture fault accounting.
>
> [1] 46e714c729c8 ("arch/mm/fault: fix major fault accounting when retrying
> under per-VMA lock")
>
> Fixes: 12214eba1992 ("mm: handle read faults under the VMA lock")
>
> [...]
Here is the summary with links:
- [1/1] arch/arm/mm: fix major fault accounting when retrying under per-VMA
lock
https://git.kernel.org/riscv/c/e870920bbe68
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH] tty: hvc: Don't enable the RISC-V SBI console by default
Hello: This patch was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Wed, 14 Feb 2024 07:34:30 -0800 you wrote: > From: Palmer Dabbelt > > The new SBI console has the same problem as the old one: there's only > one shared backing hardware and no synchronization, so the two drivers > end up stepping on each other. This was the same issue the old SBI-0.1 > console drivers had, but that was disabled by default when SBI-0.1 was. > > [...] Here is the summary with links: - tty: hvc: Don't enable the RISC-V SBI console by default https://git.kernel.org/riscv/c/481860974faa You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
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
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
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
Re: [PATCH v6 0/5] RISC-V SBI debug console extension support
Hello: This series was applied to riscv/linux.git (fixes) by Palmer Dabbelt : On Fri, 19 Jan 2024 17:04:44 +0530 you wrote: > The SBI v2.0 specification is now frozen. The SBI v2.0 specification defines > SBI debug console (DBCN) extension which replaces the legacy SBI v0.1 > functions sbi_console_putchar() and sbi_console_getchar(). > (Refer v2.0-rc5 at https://github.com/riscv-non-isa/riscv-sbi-doc/releases) > > This series adds support for SBI debug console (DBCN) extension in > Linux RISC-V. > > [...] Here is the summary with links: - [v6,1/5] RISC-V: Add stubs for sbi_console_putchar/getchar() https://git.kernel.org/riscv/c/f503b167b660 - [v6,2/5] RISC-V: Add SBI debug console helper routines (no matching commit) - [v6,3/5] tty/serial: Add RISC-V SBI debug console based earlycon https://git.kernel.org/riscv/c/c77bf3607a0f - [v6,4/5] tty: Add SBI debug console support to HVC SBI driver (no matching commit) - [v6,5/5] RISC-V: Enable SBI based earlycon support https://git.kernel.org/riscv/c/50942ad6ddb5 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH 1/1] arch/mm/fault: fix major fault accounting when retrying under per-VMA lock
Hello: This patch was applied to riscv/linux.git (fixes) by Andrew Morton : On Tue, 26 Dec 2023 13:46:10 -0800 you wrote: > A test [1] in Android test suite started failing after [2] was merged. > It turns out that after handling a major fault under per-VMA lock, the > process major fault counter does not register that fault as major. > Before [2] read faults would be done under mmap_lock, in which case > FAULT_FLAG_TRIED flag is set before retrying. That in turn causes > mm_account_fault() to account the fault as major once retry completes. > With per-VMA locks we often retry because a fault can't be handled > without locking the whole mm using mmap_lock. Therefore such retries > do not set FAULT_FLAG_TRIED flag. This logic does not work after [2] > because we can now handle read major faults under per-VMA lock and > upon retry the fact there was a major fault gets lost. Fix this by > setting FAULT_FLAG_TRIED after retrying under per-VMA lock if > VM_FAULT_MAJOR was returned. Ideally we would use an additional > VM_FAULT bit to indicate the reason for the retry (could not handle > under per-VMA lock vs other reason) but this simpler solution seems > to work, so keeping it simple. > > [...] Here is the summary with links: - [1/1] arch/mm/fault: fix major fault accounting when retrying under per-VMA lock https://git.kernel.org/riscv/c/46e714c729c8 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH v5 0/5] RISC-V SBI debug console extension support
Hello: This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Fri, 24 Nov 2023 12:39:00 +0530 you wrote: > The SBI v2.0 specification is now frozen. The SBI v2.0 specification defines > SBI debug console (DBCN) extension which replaces the legacy SBI v0.1 > functions sbi_console_putchar() and sbi_console_getchar(). > (Refer v2.0-rc5 at https://github.com/riscv-non-isa/riscv-sbi-doc/releases) > > This series adds support for SBI debug console (DBCN) extension in > Linux RISC-V. > > [...] Here is the summary with links: - [v5,1/5] RISC-V: Add stubs for sbi_console_putchar/getchar() https://git.kernel.org/riscv/c/f503b167b660 - [v5,2/5] RISC-V: Add SBI debug console helper routines https://git.kernel.org/riscv/c/f43fabf444ca - [v5,3/5] tty/serial: Add RISC-V SBI debug console based earlycon https://git.kernel.org/riscv/c/c77bf3607a0f - [v5,4/5] tty: Add SBI debug console support to HVC SBI driver https://git.kernel.org/riscv/c/88ead68e764c - [v5,5/5] RISC-V: Enable SBI based earlycon support https://git.kernel.org/riscv/c/50942ad6ddb5 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH 1/4] kbuild: remove ARCH_POSTLINK from module builds
Hello: This patch was applied to riscv/linux.git (fixes) by Masahiro Yamada : On Tue, 17 Oct 2023 19:37:39 +0900 you wrote: > The '%.ko' rule in arch/*/Makefile.postlink does nothing but call the > 'true' command. > > Remove the meaningless code. > > Signed-off-by: Masahiro Yamada > > [...] Here is the summary with links: - [1/4] kbuild: remove ARCH_POSTLINK from module builds https://git.kernel.org/riscv/c/7f6d8f7e43fb You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH v3 0/9] RISC-V SBI debug console extension support
Hello: This series was applied to riscv/linux.git (fixes) by Anup Patel : On Fri, 20 Oct 2023 12:51:31 +0530 you wrote: > The SBI v2.0 specification is now frozen. The SBI v2.0 specification defines > SBI debug console (DBCN) extension which replaces the legacy SBI v0.1 > functions sbi_console_putchar() and sbi_console_getchar(). > (Refer v2.0-rc5 at https://github.com/riscv-non-isa/riscv-sbi-doc/releases) > > This series adds support for SBI debug console (DBCN) extension in KVM RISC-V > and Linux RISC-V. > > [...] Here is the summary with links: - [v3,1/9] RISC-V: Add defines for SBI debug console extension https://git.kernel.org/riscv/c/dadf7886993c - [v3,2/9] RISC-V: KVM: Change the SBI specification version to v2.0 https://git.kernel.org/riscv/c/b88e87a0a1ec - [v3,3/9] RISC-V: KVM: Allow some SBI extensions to be disabled by default https://git.kernel.org/riscv/c/56d8a385b605 - [v3,4/9] RISC-V: KVM: Forward SBI DBCN extension to user-space https://git.kernel.org/riscv/c/c667ad229d13 - [v3,5/9] KVM: riscv: selftests: Add SBI DBCN extension to get-reg-list test https://git.kernel.org/riscv/c/d9c00f44e5de - [v3,6/9] RISC-V: Add stubs for sbi_console_putchar/getchar() (no matching commit) - [v3,7/9] tty/serial: Add RISC-V SBI debug console based earlycon (no matching commit) - [v3,8/9] tty: Add SBI debug console support to HVC SBI driver (no matching commit) - [v3,9/9] RISC-V: Enable SBI based earlycon support (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH v9 0/6] Introduce 64b relocatable kernel
Hello: This series was applied to riscv/linux.git (for-next) by Palmer Dabbelt : On Wed, 29 Mar 2023 06:53:23 +0200 you wrote: > After multiple attempts, this patchset is now based on the fact that the > 64b kernel mapping was moved outside the linear mapping. > > The first patch allows to build relocatable kernels but is not selected > by default. That patch is a requirement for KASLR. > The second and third patches take advantage of an already existing powerpc > script that checks relocations at compile-time, and uses it for riscv. > > [...] Here is the summary with links: - [v9,1/6] riscv: Prepare EFI header for relocatable kernels https://git.kernel.org/riscv/c/55de1e4ad43b - [v9,2/6] riscv: Move .rela.dyn outside of init to avoid empty relocations https://git.kernel.org/riscv/c/69a90d2fe107 - [v9,3/6] riscv: Introduce CONFIG_RELOCATABLE https://git.kernel.org/riscv/c/39b33072941f - [v9,4/6] powerpc: Move script to check relocations at compile time in scripts/ https://git.kernel.org/riscv/c/47981b5cc687 - [v9,5/6] riscv: Check relocations at compile time https://git.kernel.org/riscv/c/c2dea0bc5339 - [v9,6/6] riscv: Use --emit-relocs in order to move .rela.dyn in init https://git.kernel.org/riscv/c/559d1e45a16d You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH] mm: remove zap_page_range and create zap_vma_pages
Hello: This patch was applied to riscv/linux.git (for-next) by Andrew Morton : On Tue, 3 Jan 2023 16:27:32 -0800 you wrote: > zap_page_range was originally designed to unmap pages within an address > range that could span multiple vmas. While working on [1], it was > discovered that all callers of zap_page_range pass a range entirely within > a single vma. In addition, the mmu notification call within zap_page > range does not correctly handle ranges that span multiple vmas. When > crossing a vma boundary, a new mmu_notifier_range_init/end call pair > with the new vma should be made. > > [...] Here is the summary with links: - mm: remove zap_page_range and create zap_vma_pages https://git.kernel.org/riscv/c/e9adcfecf572 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
Re: [PATCH mm-unstable v1 00/26] mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE on all architectures with swap PTEs
Hello: This series was applied to riscv/linux.git (for-next) by Andrew Morton : On Fri, 13 Jan 2023 18:10:00 +0100 you wrote: > This is the follow-up on [1]: > [PATCH v2 0/8] mm: COW fixes part 3: reliable GUP R/W FOLL_GET of > anonymous pages > > After we implemented __HAVE_ARCH_PTE_SWP_EXCLUSIVE on most prominent > enterprise architectures, implement __HAVE_ARCH_PTE_SWP_EXCLUSIVE on all > remaining architectures that support swap PTEs. > > [...] Here is the summary with links: - [mm-unstable,v1,01/26] mm/debug_vm_pgtable: more pte_swp_exclusive() sanity checks (no matching commit) - [mm-unstable,v1,02/26] alpha/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,03/26] arc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,04/26] arm/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,05/26] csky/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,06/26] hexagon/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,07/26] ia64/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,08/26] loongarch/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,09/26] m68k/mm: remove dummy __swp definitions for nommu (no matching commit) - [mm-unstable,v1,10/26] m68k/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,11/26] microblaze/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,12/26] mips/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,13/26] nios2/mm: refactor swap PTE layout (no matching commit) - [mm-unstable,v1,14/26] nios2/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,15/26] openrisc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,16/26] parisc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,17/26] powerpc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE on 32bit book3s (no matching commit) - [mm-unstable,v1,18/26] powerpc/nohash/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,19/26] riscv/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE https://git.kernel.org/riscv/c/51a1007d4113 - [mm-unstable,v1,20/26] sh/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,21/26] sparc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE on 32bit (no matching commit) - [mm-unstable,v1,22/26] sparc/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE on 64bit (no matching commit) - [mm-unstable,v1,23/26] um/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,24/26] x86/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE also on 32bit (no matching commit) - [mm-unstable,v1,25/26] xtensa/mm: support __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) - [mm-unstable,v1,26/26] mm: remove __HAVE_ARCH_PTE_SWP_EXCLUSIVE (no matching commit) You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html
