From: Thiago Jung Bauermann <bauerman@linux•vnet.ibm.com>
To: Dave Young <dyoung@redhat•com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro•org>,
kexec@lists•infradead.org, ebiederm@xmission•com, bhe@redhat•com,
vgoyal@redhat•com, will.deacon@arm•com, catalin.marinas@arm•com,
linux-kernel@vger•kernel.org,
linux-arm-kernel@lists•infradead.org,
linuxppc-dev@lists•ozlabs.org
Subject: Re: [RFC] arm64: kexec_file_load support
Date: Fri, 08 Jul 2016 11:48:44 -0300 [thread overview]
Message-ID: <11139482.zLvCKVycQr@hactar> (raw)
In-Reply-To: <20160707061245.GA18459@dhcp-128-65.nay.redhat.com>
Am Donnerstag, 07 Juli 2016, 14:12:45 schrieb Dave Young:
> If so maybe change a bit from your precious mentioned 7 args proposal like
> below?
>
> struct kexec_file_fd {
> enum kexec_file_type;
> int fd;
> }
>
> struct kexec_fdset {
> int nr_fd;
> struct kexec_file_fd fd[0];
> }
>
> int kexec_file_load(int kernel_fd, int initrd_fd,
> unsigned long cmdline_len, const char *cmdline_ptr,
> unsigned long flags, struct kexec_fdset *extra_fds);
Is there a way for the kernel to distinguish whether the process passed 5 or
6 arguments? How can it know whether extra_fds is a valid argument or just
garbage? I think we have to define a new flag KEXEC_FILE_EXTRA_FDS so that
the process can signal that it is using the new interface.
--
[]'s
Thiago Jung Bauermann
IBM Linux Technology Center
next prev parent reply other threads:[~2016-07-08 14:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160701051111.GL20774@linaro.org>
2016-07-01 15:46 ` [RFC] arm64: kexec_file_load support Thiago Jung Bauermann
2016-07-04 6:58 ` AKASHI Takahiro
2016-07-04 22:50 ` Thiago Jung Bauermann
2016-07-05 8:07 ` AKASHI Takahiro
2016-07-05 1:25 ` Dave Young
2016-07-05 8:03 ` AKASHI Takahiro
2016-07-07 6:12 ` Dave Young
2016-07-08 14:48 ` Thiago Jung Bauermann [this message]
2016-07-11 3:10 ` Dave Young
2016-07-11 7:19 ` AKASHI Takahiro
2016-07-11 8:14 ` Dave Young
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=11139482.zLvCKVycQr@hactar \
--to=bauerman@linux$(echo .)vnet.ibm.com \
--cc=bhe@redhat$(echo .)com \
--cc=catalin.marinas@arm$(echo .)com \
--cc=dyoung@redhat$(echo .)com \
--cc=ebiederm@xmission$(echo .)com \
--cc=kexec@lists$(echo .)infradead.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=takahiro.akashi@linaro$(echo .)org \
--cc=vgoyal@redhat$(echo .)com \
--cc=will.deacon@arm$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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