This is cleanup after initrd removal
Signed-off-by: Askar Safin
---
arch/alpha/kernel/core_irongate.c| 2 +-
arch/alpha/kernel/setup.c| 2 +-
arch/arc/mm/init.c | 2 +-
arch/arm/kernel/atags_parse.c| 2 +-
This is cleanup after initrd removal
Signed-off-by: Askar Safin
---
arch/arm/mm/init.c| 2 +-
arch/loongarch/kernel/setup.c | 2 +-
arch/riscv/mm/init.c | 2 +-
include/linux/initrd.h| 4 ++--
init/initramfs.c | 2 +-
5 files changed, 6 insertions(+), 6
This is cleanup after initrd removal
Signed-off-by: Askar Safin
---
init/do_mounts.c | 2 ++
init/do_mounts.h | 10 --
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index 7ec5ee5a5c19..5b55d0035e03 100644
--- a/init/do_mounts.c
+++ b
This is cleanup after initrd removal
Signed-off-by: Askar Safin
---
init/initramfs.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/init/initramfs.c b/init/initramfs.c
index 30e94ebf4902..40c8e4b05886 100644
--- a/init/initramfs.c
+++ b/init/initramfs.c
@@ -570,13
Fix typo
Signed-off-by: Askar Safin
---
init/initramfs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/init/initramfs.c b/init/initramfs.c
index 8b648b09247a..cf19b7c0c358 100644
--- a/init/initramfs.c
+++ b/init/initramfs.c
@@ -636,7 +636,7 @@ void __init reserve_initramfs
This is cleanup after initrd removal
Signed-off-by: Askar Safin
---
init/main.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/init/main.c b/init/main.c
index cbebd64f523c..a42f1f0fce84 100644
--- a/init/main.c
+++ b/init/main.c
@@ -1587,11 +1587,11 @@ static noinlin
Initrd support was removed,
and CONFIG_RD_LZMA has nothing to do with ramdisks.
Update your configs
Signed-off-by: Askar Safin
---
arch/arm/configs/clps711x_defconfig| 2 +-
arch/arm/configs/hisi_defconfig| 2 +-
arch/arm/configs/lpc18xx_defconfig | 2 +-
arch/arm/co
On Sat, 2025-09-13 at 00:37 +, Askar Safin wrote:
> Intro
>
> This patchset removes classic initrd (initial RAM disk) support,
> which was deprecated in 2020.
> Initramfs still stays, and RAM disk itself (brd) still stays, too.
> init/do_mounts* and init/*initramfs* are listed in VFS entry
On 11.09.25 09:48, Peter Zijlstra wrote:
On Thu, Sep 11, 2025 at 08:34:19AM +0200, Juergen Gross wrote:
Some cleanups and reorg of paravirt code and headers:
- The first 2 patches should be not controversial at all, as they
remove just some no longer needed #include and struct forward
dec
On Fri, Sep 12, 2025 at 02:40:55PM +0200, David Hildenbrand wrote:
> It would just be passing more context down to the architecture, right?
Yes. Namely this one would be arch-defined and arch_enter_lazy_mmu_mode()
by default.
static inline void arch_enter_lazy_mmu_mode_pte(struct mm_struct *mm,
PowerPC FW introduced HVPIPE RTAS calls such as
ibm,send-hvpipe-msg and ibm,receive-hvpipe-msg for the user space
to exchange information with different sources such as Hardware
Management Consoles (HMC).
HVPIPE_IOC_CREATE_HANDLE is defined to use /dev/papr-hvpipe
interface for ibm,send-hvpipe-msg
From: Rohan McLure
This reverts commit 1831414cd729 ("mm/page_table_check: remove unused
parameter in [__]page_table_check_pmd_clear").
Reinstate previously unused parameters for the purpose of supporting
powerpc platforms, as many do not encode user/kernel ownership of the
page in the pte, but
On 12.09.25 16:05, Alexander Gordeev wrote:
On Fri, Sep 12, 2025 at 03:02:15PM +0200, David Hildenbrand wrote:
How would that work with nesting? I feel like there is a fundamental problem
with nesting with what you describe but I might be wrong.
My picture is - flush on each lazy_mmu_disable()
On Thu, Sep 11, 2025 at 08:07:46PM +0530, Shrikanth Hegde wrote:
>
>
> On 9/11/25 7:23 AM, Yury Norov wrote:
> > On Wed, Sep 10, 2025 at 11:12:03PM +0530, Shrikanth Hegde wrote:
> > > CPUs are marked paravirt when there is contention for underlying
> > > physical CPU.
> > >
> > > The push mechan
On Sat, Sep 13, 2025, at 12:53, Ash Logan wrote:
Hi Ash,
> All of these are flatmem devices, as that's all the 32-bit PowerPC arch
> supports, with the Wii U additionally enabling highmem for its 2GB of
> RAM. Both devices have a small memory area (MEM1) with the "bulk" of RAM
> starting at 25
config-001-20250912gcc-10.5.0
arc randconfig-001-20250913gcc-10.5.0
arc randconfig-002-20250912gcc-12.5.0
arc randconfig-002-20250913gcc-11.5.0
arcvdk_hs38_defconfiggcc-
On 9/9/25 2:32 AM, Mukesh Kumar Chaurasiya wrote:
Renaming arch_irq_disabled_regs to regs_irqs_disabled to be used
commonly in generic entry exit framework and ppc arch code.
Signed-off-by: Mukesh Kumar Chaurasiya
---
arch/powerpc/include/asm/hw_irq.h| 4 ++--
arch/powerpc/include/as
On 9/9/25 2:32 AM, Mukesh Kumar Chaurasiya wrote:
Enabling build with generic entry/exit framework for powerpc
architecture requires few necessary steps.
Introducing minor infrastructure updates to prepare for future generic
framework handling:
- Add syscall_work field to struct thread_info
Intro
This patchset removes classic initrd (initial RAM disk) support,
which was deprecated in 2020.
Initramfs still stays, and RAM disk itself (brd) still stays, too.
init/do_mounts* and init/*initramfs* are listed in VFS entry in
MAINTAINERS, so I think this patchset should go through VFS tr
Hi!
On Fri, Sep 12, 2025 at 08:21:10PM +0100, Mark Cave-Ayland wrote:
> Whilst the patch is fairly complete, the problem I have is that there
> doesn't appear to be a concise list of CPUs that use BLRM (as opposed to
> proper LE memory accesses) when MSR_LE is enabled.
*All* older PowerPC have ev
> On 12 Sep 2025, at 10:51 AM, Venkat Rao Bagalkote
> wrote:
>
> Greetings!!!
>
>
> IBM CI has reported a kernel crash, while running generic/256 test case on
> pmem device from xfstests suite on linux-next20250911 kernel.
>
>
> xfstests: git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.
From: Leon Romanovsky
General dma_direct_map_resource() is going to be removed
in next patch, so simply open-code it in xen driver.
Reviewed-by: Juergen Gross
Reviewed-by: Jason Gunthorpe
Signed-off-by: Leon Romanovsky
---
drivers/xen/swiotlb-xen.c | 21 -
1 file changed,
On Fri, Sep 12, 2025, at 11:32, Andreas Larsson wrote:
> On 2025-09-11 09:53, Arnd Bergmann wrote:
>> On Thu, Sep 11, 2025, at 07:38, Andreas Larsson wrote:
>>>
>>> We have a upcoming SoC with support for up to 16 GiB of DRAM. When that is
>>> used in LEON sparc32 configuration (using 36-bit physic
23 matches
Mail list logo