From: Vivek Goyal <vgoyal@redhat.com>
To: Simon Horman <horms@verge.net.au>
Cc: Michael Holzheu <holzheu@linux.vnet.ibm.com>,
kexec@lists.infradead.org, ying.huang@intel.com
Subject: Re: kexec: load-preserve-context option on s390
Date: Thu, 29 Sep 2011 09:32:09 -0400 [thread overview]
Message-ID: <20110929133209.GA25760@redhat.com> (raw)
In-Reply-To: <20110928235101.GB13684@verge.net.au>
On Thu, Sep 29, 2011 at 08:51:02AM +0900, Simon Horman wrote:
> On Mon, Sep 26, 2011 at 03:09:09PM +0200, Michael Holzheu wrote:
> > Hello Simon,
> >
> > I think the --load-preserve-context and --load-jump-back-helper kexec
> > options are not working on s390 because we do not support
> > CONFIG_KEXEC_JUMP. I assume the same is true also on other
> > architectures. Correct me, if I am wrong. Unfortunately I did not find
> > much documentation for that feature.
> >
> > Wouldn't it be better to print an error message when the options are
> > used on those architectures?
>
> Ideally it would be nice if kexec-tools could ask the kernel
> if KEXEC_JUMP is supported (or enabled?) or not rather than
> hardcoding this information into kexec-tools on a per-architecture basis.
Shouldn't kexec system call return error if KEXEC_JUMP is not supported
and user asked for it?
Thanks
Vivek
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2011-09-29 13:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 13:09 kexec: load-preserve-context option on s390 Michael Holzheu
2011-09-28 23:51 ` Simon Horman
2011-09-29 13:32 ` Vivek Goyal [this message]
2011-09-29 13:38 ` Michael Holzheu
2011-09-30 16:06 ` Vivek Goyal
2011-10-04 14:07 ` Michael Holzheu
2011-10-04 14:55 ` Vivek Goyal
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=20110929133209.GA25760@redhat.com \
--to=vgoyal@redhat.com \
--cc=holzheu@linux.vnet.ibm.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=ying.huang@intel.com \
/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