From: Sourabh Jain <sourabhjain@linux.ibm.com>
To: Eric DeVolder <eric.devolder@oracle.com>,
linuxppc-dev@ozlabs.org, mpe@ellerman.id.au
Cc: kexec@lists.infradead.org, hbathini@linux.ibm.com, bhe@redhat.com
Subject: Re: [RFC v3 PATCH 3/5] powrepc/crash hp: update kimage struct
Date: Thu, 24 Mar 2022 11:37:27 +0530 [thread overview]
Message-ID: <1d9a3eaf-191c-da35-3628-38e8c0ad54bc@linux.ibm.com> (raw)
In-Reply-To: <8fc2d63d-97db-59ab-3043-d453fed1e7e3@oracle.com>
Hello Eric,
On 24/03/22 00:02, Eric DeVolder wrote:
>
>
> On 3/21/22 03:04, 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;
>> + int fdt_index;
>> + bool fdt_index_valid;
>> unsigned long backup_start;
>> void *backup_buf;
>> void *fdt;
>>
>
> Question, for the kexec_file_load scenario, is there a need to have
> the fdt_index segment excluded by kexec_calculate_store_digests() ?
On PowerPC, SHA verification is not done for kexec_file_load system
call, so we might not need to exclude the FDT segment.
Thanks for the review.
- Sourabh Jain
next prev parent reply other threads:[~2022-03-24 6:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 8:04 [RFC v3 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 1/5] powerpc/kexec: make update_cpus_node non-static Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 2/5] powerpc/crash hp: introduce a new config option CRASH_HOTPLUG Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-21 8:04 ` [RFC v3 PATCH 3/5] powrepc/crash hp: update kimage struct Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-24 6:07 ` Sourabh Jain [this message]
2022-03-21 8:04 ` [RFC v3 PATCH 4/5] powerpc/crash hp: add crash hotplug support for kexec_file_load Sourabh Jain
2022-03-23 18:32 ` Eric DeVolder
2022-03-25 11:32 ` Sourabh Jain
2022-03-25 18:03 ` Laurent Dufour
2022-03-31 9:00 ` Sourabh Jain
2022-03-21 8:04 ` [RFC v3 PATCH 5/5] powerpc/crash hp: add crash hotplug support for kexec_load Sourabh Jain
2022-03-23 18:33 ` Eric DeVolder
2022-03-23 18:32 ` [RFC v3 PATCH 0/5] In kernel handling of CPU hotplug events for crash kernel Eric DeVolder
2022-03-25 8:32 ` Sourabh Jain
2022-03-25 17:04 ` Laurent Dufour
2022-03-31 9:05 ` Sourabh Jain
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=1d9a3eaf-191c-da35-3628-38e8c0ad54bc@linux.ibm.com \
--to=sourabhjain@linux.ibm.com \
--cc=bhe@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=hbathini@linux.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mpe@ellerman.id.au \
/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;
as well as URLs for NNTP newsgroup(s).