Re: [PATCH v2 1/3] sysfs: constify bin_attribute argument of sysfs_bin_attr_simple_read()

@@ -196,7 +196,7 @@ static int add_notes_attrs(struct module *mod, const > struct load_info *info) > nattr->attr.mode = 0444; > nattr->size = info->sechdrs[i].sh_size; > nattr->private = (void *)info->sechdrs[i].sh_addr; > - nattr->read = sysfs_bin_attr_simple_read; > + nattr->read_new = sysfs_bin_attr_simple_read; > ++nattr; > } > ++loaded; > > -- > 2.47.1 > > -- Mahesh J Salgaonkar

[RFC PATCH v6 2/4] powerpc/fadump: Reservationless firmware assisted dump

From: Mahesh Salgaonkar One of the primary issues with Firmware Assisted Dump (fadump) on Power is that it needs a large amount of memory to be reserved. On large systems with TeraBytes of memory, this reservation can be quite significant. In some cases, fadump fails if the memory reserved is in

[RFC PATCH v6 4/4] powerpc/fadump: Do not allow hot-remove memory from fadump reserved area.

From: Mahesh Salgaonkar For fadump to work successfully there should not be any holes in reserved memory ranges where kernel has asked firmware to move the content of old kernel memory in event of crash. Now that fadump reserved memory is marked as movable zone, this memory area is now not protec

[RFC PATCH v6 3/4] powerpc/fadump: throw proper error message on fadump registration failure.

From: Mahesh Salgaonkar fadump fails to register when there are holes in reserved memory area. This can happen if user has hot-removed a memory that falls in the fadump reserved memory area. Throw a meaningful error message to the user in such case. Signed-off-by: Mahesh Salgaonkar --- arch/po

[RFC PATCH v6 1/4] mm/page_alloc: Introduce an interface to mark reserved memory as ZONE_MOVABLE

From: Mahesh Salgaonkar Add an interface to allow a custom reserved memory to be marked as ZONE_MOVABLE. This will help some subsystem's to convert their reserved memory region into ZONE_MOVABLE so that the memory can still be available to user applications. The approach is based on Joonsoo Kim'

[RFC PATCH v6 0/4] powerpc/fadump: Improvements and fixes for firmware-assisted dump.

One of the primary issues with Firmware Assisted Dump (fadump) on Power is that it needs a large amount of memory to be reserved. This reserved memory is used for saving the contents of old crashed kernel's memory before fadump capture kernel uses old kernel's memory area to boot. However, This res

[PATCH 2/2] powerpc/book3s: mce: Use add_taint_no_warn() in machine_check_early().

From: Mahesh Salgaonkar machine_check_early() gets called in real mode. The very first time when add_taint() is called, it prints a warning which ends up calling opal call (that uses OPAL_CALL wrapper) for writing it to console. If we get a very first machine check while we are in opal we are doo

[PATCH 1/2] Introduce add_taint variant that does not print warning.

From: Mahesh Salgaonkar Some interrupt handler's may not be happy to call printk and would lead to unexpected behavior or kernel panic. e.g. machine_check_early() from MCE handler on OPAL based system. Introduce add_taint variant that does not call printk. Signed-off-by: Mahesh Salgaonkar ---

[PATCH] powerpc: Fix "attempt to move .org backwards" error

From: Mahesh Salgaonkar With recent machine check patch series changes, The exception vectors starting from 0x4300 are now overflowing with allyesconfig. Fix that by moving machine_check_common and machine_check_handle_early code out of that region to make enough room for exception vector area.