From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: kexec@lists.infradead.org
Subject: [RFC v4 PATCH 3/5] powrepc/crash hp: update kimage_arch struct
Date: Tue, 19 Apr 2022 13:51:48 +0530 [thread overview]
Message-ID: <44105142-5a4b-28c9-243a-e116cd1c3c36@linux.ibm.com> (raw)
In-Reply-To: <57f1960f-4fc7-6061-0fc2-b2bfd09b334f@linux.ibm.com>
On 14/04/22 22:05, Laurent Dufour wrote:
> On 11/04/2022, 10:43:55, Sourabh Jain wrote:
>> Two new members fdt_index and fdt_index_valid are added in kimage_arch
>> struct to track the FDT kexec segment. These new members of kimage_arch
>> struct will help the crash hotplug handler to easily access the FDT
>> segment from the kexec segment array. Otherwise, we have to loop through
>> all kexec segments to find the FDT segments.
>>
>> Signed-off-by: Sourabh Jain <sourabhjain@linux.ibm.com>
>> ---
>> arch/powerpc/include/asm/kexec.h | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/arch/powerpc/include/asm/kexec.h b/arch/powerpc/include/asm/kexec.h
>> index e1288826e22e..19c2cab6a880 100644
>> --- a/arch/powerpc/include/asm/kexec.h
>> +++ b/arch/powerpc/include/asm/kexec.h
>> @@ -104,6 +104,8 @@ extern const struct kexec_file_ops kexec_elf64_ops;
>> struct kimage_arch {
>> struct crash_mem *exclude_ranges;
>>
> #ifdef CONFIG_CRASH_HOTPLUG ?
>> + int fdt_index;
>> + bool fdt_index_valid;
> #endif
>
> It seems that this is only used when CONFIG_CRASH_HOTPLUG is defined, isn't it?
Yes it should be kept under CONFIG_CRASH_HOTPLUG config.
Thanks,
Sourabh Jain
>
>> unsigned long backup_start;
>> void *backup_buf;
>> void *fdt;
next prev parent reply other threads:[~2022-04-19 8:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 8:43 [RFC v4 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel Sourabh Jain
2022-04-11 8:43 ` [RFC v4 PATCH 1/5] powerpc/kexec: make update_cpus_node non-static Sourabh Jain
2022-04-11 8:43 ` [RFC v4 PATCH 2/5] powerpc/crash hp: introduce a new config option CRASH_HOTPLUG Sourabh Jain
2022-04-14 16:40 ` Laurent Dufour
2022-04-19 8:20 ` Sourabh Jain
2022-04-21 11:34 ` Michael Ellerman
2022-04-21 15:29 ` Eric DeVolder
2022-04-22 4:22 ` Michael Ellerman
2022-04-26 4:10 ` Sourabh Jain
2022-04-26 3:47 ` Sourabh Jain
2022-04-11 8:43 ` [RFC v4 PATCH 3/5] powrepc/crash hp: update kimage_arch struct Sourabh Jain
2022-04-14 16:35 ` Laurent Dufour
2022-04-19 8:21 ` Sourabh Jain [this message]
2022-04-11 8:43 ` [RFC v4 PATCH 4/5] powerpc/crash hp: add crash hotplug support for kexec_file_load Sourabh Jain
2022-04-14 16:32 ` Laurent Dufour
2022-04-19 8:31 ` Sourabh Jain
2022-04-21 15:33 ` Eric DeVolder
2022-04-11 8:43 ` [RFC v4 PATCH 5/5] powerpc/crash hp: add crash hotplug support for kexec_load Sourabh Jain
2022-04-14 16:39 ` Laurent Dufour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44105142-5a4b-28c9-243a-e116cd1c3c36@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=kexec@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox