From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: keir@xen.org, Kees Cook <keescook@chromium.org>,
Richard Weinberger <richard.weinberger@gmail.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
kexec@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>,
xen-devel@lists.xen.org, hbabu@us.ibm.com,
"Eric W. Biederman" <ebiederm@xmission.com>,
jbeulich@suse.com, "H. Peter Anvin" <hpa@linux.intel.com>,
david.vrabel@citrix.com
Subject: Re: kexec: Clearing registers just before jumping into purgatory
Date: Fri, 11 Oct 2013 17:56:22 +0100 [thread overview]
Message-ID: <20131011165622.GC32133@srcf.ucam.org> (raw)
In-Reply-To: <20131011165351.GC2772@redhat.com>
On Fri, Oct 11, 2013 at 12:53:51PM -0400, Vivek Goyal wrote:
> On Fri, Oct 11, 2013 at 05:44:00PM +0100, Matthew Garrett wrote:
> > I have /dev/mem and a list of addresses I want to modify.
>
> Why to boot in a second kernel to modify first kernel's RAM. Why not
> do it directly from the first kernel itself (until and unless we want
> first kernel to be stopped while doing those modifications).
Because the kernel in question won't let me do that.
--
Matthew Garrett | mjg59@srcf.ucam.org
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Vivek Goyal <vgoyal@redhat.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
hbabu@us.ibm.com, "H. Peter Anvin" <hpa@linux.intel.com>,
Kees Cook <keescook@chromium.org>,
kexec@lists.infradead.org, LKML <linux-kernel@vger.kernel.org>,
david.vrabel@citrix.com, jbeulich@suse.com, keir@xen.org,
xen-devel@lists.xen.org
Subject: Re: kexec: Clearing registers just before jumping into purgatory
Date: Fri, 11 Oct 2013 17:56:22 +0100 [thread overview]
Message-ID: <20131011165622.GC32133@srcf.ucam.org> (raw)
In-Reply-To: <20131011165351.GC2772@redhat.com>
On Fri, Oct 11, 2013 at 12:53:51PM -0400, Vivek Goyal wrote:
> On Fri, Oct 11, 2013 at 05:44:00PM +0100, Matthew Garrett wrote:
> > I have /dev/mem and a list of addresses I want to modify.
>
> Why to boot in a second kernel to modify first kernel's RAM. Why not
> do it directly from the first kernel itself (until and unless we want
> first kernel to be stopped while doing those modifications).
Because the kernel in question won't let me do that.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2013-10-11 16:56 UTC|newest]
Thread overview: 63+ 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 9:28 ` Daniel Kiper
2013-10-11 10:08 ` Eric W. Biederman
2013-10-11 10:08 ` Eric W. Biederman
2013-10-11 10:08 ` Eric W. Biederman
2013-10-11 11:04 ` Daniel Kiper
2013-10-11 11:04 ` Daniel Kiper
2013-10-11 12:52 ` Vivek Goyal
2013-10-11 12:52 ` Vivek Goyal
2013-10-11 15:37 ` Matthew Garrett
2013-10-11 15:37 ` Matthew Garrett
2013-10-11 15:44 ` Vivek Goyal
2013-10-11 15:44 ` Vivek Goyal
2013-10-11 15:44 ` Vivek Goyal
2013-10-11 15:48 ` Matthew Garrett
2013-10-11 15:48 ` Matthew Garrett
2013-10-11 15:48 ` Matthew Garrett
2013-10-11 16:33 ` Richard Weinberger
2013-10-11 16:33 ` Richard Weinberger
2013-10-11 16:33 ` Richard Weinberger
2013-10-11 16:39 ` Matthew Garrett
2013-10-11 16:39 ` Matthew Garrett
2013-10-11 16:42 ` Richard Weinberger
2013-10-11 16:42 ` Richard Weinberger
2013-10-11 16:42 ` Richard Weinberger
2013-10-11 16:44 ` Matthew Garrett
2013-10-11 16:44 ` Matthew Garrett
2013-10-11 16:44 ` Matthew Garrett
2013-10-11 16:47 ` Richard Weinberger
2013-10-11 16:47 ` Richard Weinberger
2013-10-11 16:55 ` Matthew Garrett
2013-10-11 16:55 ` Matthew Garrett
2013-10-11 16:55 ` Matthew Garrett
2013-10-11 16:59 ` Richard Weinberger
2013-10-11 16:59 ` Richard Weinberger
2013-10-11 17:01 ` Matthew Garrett
2013-10-11 17:01 ` Matthew Garrett
2013-10-11 20:44 ` Eric W. Biederman
2013-10-11 20:44 ` Eric W. Biederman
2013-10-11 20:50 ` Matthew Garrett
2013-10-11 20:50 ` Matthew Garrett
2013-10-11 20:50 ` Matthew Garrett
2013-10-11 20:44 ` Eric W. Biederman
2013-10-11 17:01 ` Matthew Garrett
2013-10-11 16:59 ` Richard Weinberger
2013-10-11 16:47 ` Richard Weinberger
2013-10-11 16:53 ` Vivek Goyal
2013-10-11 16:53 ` Vivek Goyal
2013-10-11 16:53 ` Vivek Goyal
2013-10-11 16:56 ` Matthew Garrett
2013-10-11 16:56 ` Matthew Garrett [this message]
2013-10-11 16:56 ` Matthew Garrett
2013-10-11 16:39 ` Matthew Garrett
2013-10-11 15:37 ` Matthew Garrett
2013-10-11 12:52 ` Vivek Goyal
2013-10-11 22:15 ` Eric W. Biederman
2013-10-11 22:15 ` Eric W. Biederman
2013-10-14 18:24 ` Daniel Kiper
2013-10-14 18:24 ` Daniel Kiper
2013-10-14 18:24 ` Daniel Kiper
2013-10-11 22:15 ` Eric W. Biederman
2013-10-11 11:04 ` Daniel Kiper
-- strict thread matches above, loose matches on Subject: below --
2013-10-11 9:28 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=20131011165622.GC32133@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=richard.weinberger@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.