On 06/13/16 at 04:08pm, Thiago Jung Bauermann wrote:
> Hello Dave,
>
> Thanks for the quick review and for your comments.
>
> I'll separate the change to add arch_walk_system_ram and the change to add
> kexec_locate_mem_hole into different patches, and add error handling for
> KEXEC_ON_CRASH.
>
Hi Dave,
Am Montag, 13 Juni 2016, 16:08:19 schrieb Thiago Jung Bauermann:
> Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young:
> > On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote:
> > > Allow architectures to specify different memory walking functions for
> > > kexec_add_buffer. Intel uses
Hello Dave,
Thanks for the quick review and for your comments.
I'll separate the change to add arch_walk_system_ram and the change to add
kexec_locate_mem_hole into different patches, and add error handling for
KEXEC_ON_CRASH.
Am Montag, 13 Juni 2016, 15:29:39 schrieb Dave Young:
> On 06/12/16
On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote:
> Allow architectures to specify different memory walking functions for
> kexec_add_buffer. Intel uses iomem to track reserved memory ranges,
> but PowerPC uses the memblock subsystem.
Can the crashk_res be inserted to iomem_resource so that onl
On 06/12/16 at 12:10am, Thiago Jung Bauermann wrote:
> Allow architectures to specify different memory walking functions for
> kexec_add_buffer. Intel uses iomem to track reserved memory ranges,
> but PowerPC uses the memblock subsystem.
>
> Also, factor kexec_locate_mem_hole out of kexec_add_buff
Allow architectures to specify different memory walking functions for
kexec_add_buffer. Intel uses iomem to track reserved memory ranges,
but PowerPC uses the memblock subsystem.
Also, factor kexec_locate_mem_hole out of kexec_add_buffer. It will be
used by the PowerPC kexec_file_load implementati
6 matches
Mail list logo