From: Gerd Hoffmann <kraxel@suse.de>
To: Mark Williamson <mark.williamson@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Horms <horms@verge.net.au>
Subject: Re: Re: [PATCH] Xen Guest Kexec
Date: Mon, 27 Feb 2006 16:39:48 +0100 [thread overview]
Message-ID: <44031D44.9010606@suse.de> (raw)
In-Reply-To: <200602271429.11577.mark.williamson@cl.cam.ac.uk>
> When I was looking at this approach I was intending to retreive the pageframe
> info from Xen and just run unpin on anything pinned, according to its type.
Is that possible? As far I know the frametable where that info is
stored isn't readable by domains ...
> A really big chunk of the generic kexec code is there to make sure the new
> kernel is not loaded in an area that conflicts with its destination, much of
> the trampoline is there to enable the new kernel to be copied on top of the
> old one. Address conflicts should only be an issue if you want the second
> kernel to be a dump kernel, in which case it needs to run in-place after
> loading.
Yep, sure, all the trampoline stuff is effectively for that.
Retested, works. Not sure what I did wrong last time ...
cheers,
Gerd
--
Gerd 'just married' Hoffmann <kraxel@suse.de>
I'm the hacker formerly known as Gerd Knorr.
http://www.suse.de/~kraxel/just-married.jpeg
next prev parent reply other threads:[~2006-02-27 15:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-07 17:16 [PATCH] Xen Guest Kexec Mark Williamson
2005-07-08 8:59 ` [Fastboot] " Eric W. Biederman
2005-07-08 14:35 ` Mark Williamson
2005-07-08 17:35 ` Mark Williamson
2006-02-23 10:52 ` Horms
2006-02-23 11:22 ` Gerd Hoffmann
2006-02-23 11:32 ` Mark Williamson
2006-02-23 13:03 ` Gerd Hoffmann
2006-02-23 14:49 ` Mark Williamson
2006-02-24 14:35 ` Gerd Hoffmann
2006-02-27 14:29 ` Mark Williamson
2006-02-27 15:39 ` Gerd Hoffmann [this message]
2006-02-23 11:36 ` Mark Williamson
2006-02-27 3:32 ` Horms
2006-02-27 14:58 ` Mark Williamson
-- strict thread matches above, loose matches on Subject: below --
2006-02-26 22:49 Ian Pratt
2006-02-27 7:10 ` Keir Fraser
2006-02-27 15:34 ` Gerd Hoffmann
2006-02-27 16:19 ` Keir Fraser
2006-03-01 12:09 ` Gerd Hoffmann
2006-03-01 14:10 ` Gerd Hoffmann
2006-03-01 15:03 ` Keir Fraser
2006-03-01 17:35 ` Keir Fraser
2006-03-02 9:16 ` Gerd Hoffmann
2006-03-02 9:43 ` Keir Fraser
2006-03-02 11:34 ` Gerd Hoffmann
2006-03-02 11:55 ` Keir Fraser
2006-03-02 16:36 ` Gerd Hoffmann
2006-03-02 16:48 ` Keir Fraser
2006-03-03 8:39 ` Gerd Hoffmann
2006-03-03 9:14 ` Keir Fraser
2006-03-03 9:35 ` Keir Fraser
2006-03-03 11:19 ` Gerd Hoffmann
2006-03-06 14:15 ` Gerd Hoffmann
2006-03-06 16:04 ` Michael Vrable
2006-03-07 13:06 ` Gerd Hoffmann
2006-03-07 13:42 ` Keir Fraser
2006-03-07 14:43 ` Gerd Hoffmann
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=44031D44.9010606@suse.de \
--to=kraxel@suse.de \
--cc=horms@verge.net.au \
--cc=mark.williamson@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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 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.