[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] kexec: Clearing registers just before jumping into purgatory
- To: Vivek Goyal <vgoyal@xxxxxxxxxx>
- From: Matthew Garrett <mjg59@xxxxxxxxxxxxx>
- Date: Fri, 11 Oct 2013 17:56:22 +0100
- Cc: keir@xxxxxxx, Kees Cook <keescook@xxxxxxxxxxxx>, Richard Weinberger <richard.weinberger@xxxxxxxxx>, Daniel Kiper <daniel.kiper@xxxxxxxxxx>, kexec@xxxxxxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxx, hbabu@xxxxxxxxxx, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx>, jbeulich@xxxxxxxx, "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>, david.vrabel@xxxxxxxxxx
- Delivery-date: Fri, 11 Oct 2013 16:57:03 +0000
- List-id: Xen developer discussion <xen-devel.lists.xen.org>
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@xxxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel
|
