From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: keir@xen.org, keescook@chromium.org,
Daniel Kiper <daniel.kiper@oracle.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xen.org, hbabu@us.ibm.com, ebiederm@xmission.com,
jbeulich@suse.com, hpa@linux.intel.com, david.vrabel@citrix.com
Subject: Re: kexec: Clearing registers just before jumping into purgatory
Date: Fri, 11 Oct 2013 16:48:05 +0100 [thread overview]
Message-ID: <20131011154805.GB30181@srcf.ucam.org> (raw)
In-Reply-To: <20131011154450.GB2772@redhat.com>
On Fri, Oct 11, 2013 at 11:44:50AM -0400, Vivek Goyal wrote:
> Just Curious. How is it useful. IOW, what's your use case of booting a new
> kernel and then jumping back.
I'm kexecing into a kernel with a modified /dev/mem, modifying the
original kernel and then jumping back into it.
--
Matthew Garrett | mjg59@srcf.ucam.org
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2013-10-11 15:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 9:28 kexec: Clearing registers just before jumping into purgatory Daniel Kiper
2013-10-11 10:08 ` Eric W. Biederman
2013-10-11 11:04 ` Daniel Kiper
2013-10-11 12:52 ` Vivek Goyal
2013-10-11 15:37 ` Matthew Garrett
2013-10-11 15:44 ` Vivek Goyal
2013-10-11 15:48 ` Matthew Garrett [this message]
2013-10-11 16:33 ` Richard Weinberger
2013-10-11 16:39 ` Matthew Garrett
2013-10-11 16:42 ` Richard Weinberger
2013-10-11 16:44 ` Matthew Garrett
2013-10-11 16:47 ` Richard Weinberger
2013-10-11 16:55 ` Matthew Garrett
2013-10-11 16:59 ` Richard Weinberger
2013-10-11 17:01 ` Matthew Garrett
2013-10-11 20:44 ` Eric W. Biederman
2013-10-11 20:50 ` Matthew Garrett
2013-10-11 16:53 ` Vivek Goyal
2013-10-11 16:56 ` Matthew Garrett
2013-10-11 22:15 ` Eric W. Biederman
2013-10-14 18:24 ` Daniel Kiper
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=20131011154805.GB30181@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=daniel.kiper@oracle.com \
--cc=david.vrabel@citrix.com \
--cc=ebiederm@xmission.com \
--cc=hbabu@us.ibm.com \
--cc=hpa@linux.intel.com \
--cc=jbeulich@suse.com \
--cc=keescook@chromium.org \
--cc=keir@xen.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@redhat.com \
--cc=xen-devel@lists.xen.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