On Thu, May 25, 2006 at 04:20:19PM +0900, Horms wrote:
> Hi,
>
> sorry for the somewhat long delay between sending updates.
> I'm happy to announce tenth take of the kexec/kdump patch.
> I'll address Keir's questions from the 9th release below,
> but first I would like to quickly summarise the patches.
>
> Kexec/kdump is implemented by moving the privelaged portions
> (and related plumbing where needed) from linux into the hypervisor.
> This is primarily done by implementing kexec's architecture
> independent hooks as hypercalls.
>
> Both Kexec is working for x86_32 and x86_64 for SMP and UP.
> Kdump is also working for SMP and UP on x86_32. x86_64 may work,
> but still needs more attention. In particular the register
> saving code has not been implemented.
>
> These patches also include some reworking of kexec's internals in
> order that the page table is not mangled on kdump. These changes
> also make x86_64 kexec/kdump somewhat easier to implement.
> Collectively this is the pagetable_a approach developed by my colleague
> Magnus Damm, and he is working with the linux kexec maintainers to
> get it merged there.
>
> The code is broken out into four patches.
> They should apply cleanly to xen-unstable.hg 10151.
>
> 1. 51.1-kexec-generic-upstream.patch
> * Common code for all architectures,
>
> the basic plumbing for kexec/kdump
> 2. 51.2.1-kexec-x86-upstream.patch
> * Glue between 1, and 3 and 4.
> This would not be needed for ppc or ia64, but
> neither have been written yet.
> We are planning to commence work on ia64 soon.
> * Depends on 1
>
> 3. 51.2.1.1-kexec-x86_32-upstream.patch
> * Kexec/kdump for x86_32
> * Depends on 2 (and 1)
>
> 4. 51.2.31.2-kexec-x86_64-upstream.patch
> * * Kexec/kdump for x86_64
> * Depends on 2 (and 1)
Hi,
here is a modest update to the kexec patches, broken out as per the
description above. The changes are:
* Kconfig: don't allow kexec to be build for a non-privelaged domain as
this makes no sense at this time.
* fix a gcc compilation error that became apparent in
gcc (GCC) 4.1.2 20060604 (prerelease) (Debian 4.1.1-2).
There is a warning produced that causes the build to fail because of the
use of -Werror when compiling the hypervisor. The warning relates
to kexec's use of xchg as a simple locking mechanism and not always
using the return value as it isn't of any value.
* Record dom0's cr3 in vmcore for analysis by crash
https://www.redhat.com/archives/crash-utility/2006-June/msg00015.html
* Upport from xen-unstable.hg 10151 to 10352, which is the current tree
at present. This involved fixing two minor diffing issues, nothing more.
--
Horms http://www.vergenet.net/~horms/
51.1-kexec-generic-upstream.patch
Description: Text document
51.2.1-kexec-x86-upstream.patch
Description: Text document
51.2.1.1-kexec-x86_32-upstream.patch
Description: Text document
51.2.1.2-kexec-x86_64-upstream.patch
Description: Text document
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|