From: Hari Bathini <hbathini@linux.vnet.ibm.com>
To: Simon Horman <horms@verge.net.au>,
Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: Geoff Levand <geoff@infradead.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Kexec-ml <kexec@lists.infradead.org>
Subject: Re: [PATCH] kexec/ppc64: leverage kexec_file_load support
Date: Mon, 26 Mar 2018 14:19:28 +0530 [thread overview]
Message-ID: <1f041adb-5f93-d71f-ea53-833dc504b00e@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180326071903.r2ce5tigwgc3o4tm@verge.net.au>
On Monday 26 March 2018 12:49 PM, Simon Horman wrote:
> On Mon, Mar 19, 2018 at 03:57:11PM -0300, Thiago Jung Bauermann wrote:
>> Hello Hari,
>>
>> Hari Bathini <hbathini@linux.vnet.ibm.com> writes:
>>
>>> PPC64 kernel now supports kexec_file_load system call. Leverage it by
>>> enabling that support here. Note that loading crash kernel with this
>>> system call is not yet supported in the kernel and trying to load one
>>> will fail with '-ENOTSUPP' error.
>>>
>>> Signed-off-by: Hari Bathini <hbathini@linux.vnet.ibm.com>
>>> ---
>>> kexec/arch/ppc64/kexec-elf-ppc64.c | 84 ++++++++++++++++++++++++++++++++++++
>>> kexec/kexec-syscall.h | 3 +
>>> 2 files changed, 87 insertions(+)
>> Thanks for implementing this! Looks good to me, just one nit below.
>> Regardless of that:
>>
>> Reviewed-by: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Thanks for reviewing..
>>> diff --git a/kexec/arch/ppc64/kexec-elf-ppc64.c b/kexec/arch/ppc64/kexec-elf-ppc64.c
>>> index ddd3de8..2742cd6 100644
>>> --- a/kexec/arch/ppc64/kexec-elf-ppc64.c
>>> +++ b/kexec/arch/ppc64/kexec-elf-ppc64.c
>> <snip>
>>
>>> @@ -117,6 +196,9 @@ int elf_ppc64_load(int argc, char **argv, const char *buf, off_t len,
>>> uint32_t my_run_at_load;
>>> unsigned int slave_code[256/sizeof (unsigned int)], master_entry;
>>>
>>> + if (info->file_mode)
>>> + return elf_ppc64_load_file(argc, argv, info);
>>> +
>>> /* See options.h -- add any more there, too. */
>>> static const struct option options[] = {
>>> KEXEC_ARCH_OPTIONS
>> This is placing executable code between variable declarations. It may be
>> fine for gcc but it's more idiomatic C to put it after all variable
>> declarations. But perhaps the kexec-tools style is fine with it?
> I'd rather we avoid proliferating this style in the kexec code.
> Hari, could you respin this patch?
>
Posted v2 with the necessary change...
Thanks
Hari
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2018-03-26 8:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 19:00 [PATCH] kexec/ppc64: leverage kexec_file_load support Hari Bathini
2018-03-19 18:57 ` Thiago Jung Bauermann
2018-03-26 7:19 ` Simon Horman
2018-03-26 8:49 ` Hari Bathini [this message]
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=1f041adb-5f93-d71f-ea53-833dc504b00e@linux.vnet.ibm.com \
--to=hbathini@linux.vnet.ibm.com \
--cc=bauerman@linux.vnet.ibm.com \
--cc=geoff@infradead.org \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.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