[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20131011165622.GC32133@srcf.ucam.org>
Date: Fri, 11 Oct 2013 17:56:22 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: Vivek Goyal <vgoyal@...hat.com>
Cc: Richard Weinberger <richard.weinberger@...il.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
"Eric W. Biederman" <ebiederm@...ssion.com>, hbabu@...ibm.com,
"H. Peter Anvin" <hpa@...ux.intel.com>,
Kees Cook <keescook@...omium.org>, kexec@...ts.infradead.org,
LKML <linux-kernel@...r.kernel.org>, david.vrabel@...rix.com,
jbeulich@...e.com, keir@....org, xen-devel@...ts.xen.org
Subject: Re: kexec: Clearing registers just before jumping into purgatory
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@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists