Re: [PATCH] net: Use of_property_read_bool() for boolean properties

Rob Herring writes: > It is preferred to use typed property access functions (i.e. > of_property_read_ functions) rather than low-level > of_get_property/of_find_property functions for reading properties. > Convert reading boolean properties to to of_property_read_bool(). > > Signed-off-by: Rob H

Re: [PATCH v2 0/2] Improving calls to kvmppc_hv_entry

Hi everyone, Anyone interested in reviewing this small patch-set ? I tested it on P8 and it works fine. Thanks. On 2023-03-06 07:37:38, Kautuk Consul wrote: > - remove .global scope of kvmppc_hv_entry > - remove r4 argument to kvmppc_hv_entry as it is not required > > Changes since v1: > - repl

Re: [PATCH] cpufreq: pmac32: Use of_property_read_bool() for boolean properties

On 10-03-23, 08:47, Rob Herring wrote: > It is preferred to use typed property access functions (i.e. > of_property_read_ functions) rather than low-level > of_get_property/of_find_property functions for reading properties. > Convert reading boolean properties to to of_property_read_bool(). > > Si

[PATCH v9 6/6] powerpc/kexec: add crash memory hotplug support

Extend PowerPC arch crash hotplug handler to support memory hotplug events. Since elfcorehdr is used to exchange the memory info between the kernels hence it needs to be recreated to reflect the changes due to memory hotplug events. The way memory hotplug events are handled on PowerPC and the noti

[PATCH v9 5/6] crash: forward memory_notify args to arch crash hotplug handler

On PowePC memblock regions are used to prepare elfcorehdr which describes the memory regions of the running kernel to the kdump kernel. Since the notifier used for the memory hotplug crash handler gets initiated before the update of the memblock region happens (as depicted below) for the memory rem

[PATCH v9 0/6] PowerPC: in kernel handling of CPU hotplug events for crash kernel

The Problem: Post hotplug/DLPAR events the capture kernel holds stale information about the system. Dump collection with stale capture kernel might end up in dump capture failure or an inaccurate dump collection. Existing solution: == The existing solution to keep the

[PATCH v9 4/6] powerpc/crash: add crash CPU hotplug support

Introduce PowerPC crash hotplug handler to update the necessary kexec segments in the kernel on CPU/Memory hotplug events. Currently, these updates are done by monitoring CPU/Memory hotplug events in userspace. A common crash hotplug handler is triggered from generic infrastructure for both CPU/Me

[PATCH v9 3/6] powerpc/crash: add a new member to the kimage_arch struct

A new member "fdt_index" is added to the kimage_arch struct to hold the index of the FDT (Flattened Device Tree) segment from the kexec the segment array. fdt_index will provide direct access to the FDT segment in the kexec segment array after the kdump kernel is loaded. The new attribute will be

[PATCH v9 2/6] powerpc/crash: introduce a new config option CRASH_HOTPLUG

Due to CPU/Memory hotplug events the system resources changes. A similar change should reflect in the loaded kdump kernel image that describes the state of the CPU and memory of the running kernel. If the kdump kernel image is not updated after the CPU or Memory hotplug events and it tries to coll

[PATCH v9 1/6] powerpc/kexec: turn some static helper functions public

Move update_cpus_node and get_crash_memory_ranges functions from kexec/file_load.c to kexec/core_64.c to make these functions usable by other kexec compoenets. Later in the series, these functions are utilized to do in-kernel update to kexec segments on CPU/Memory hotplug events for both kexec_loa

Re: [PATCH] net: Use of_property_read_bool() for boolean properties

On 10.03.2023 08:47:16, Rob Herring wrote: > It is preferred to use typed property access functions (i.e. > of_property_read_ functions) rather than low-level > of_get_property/of_find_property functions for reading properties. > Convert reading boolean properties to to of_property_read_bool(). >