[Xen-ia64-devel] Re: [patch 00/12] Kexec: EFI Mapping: Take IV

[Alex Williamson <alex.williamson@xxxxxx>]

Hi Simon,

   Sorry I haven't gotten a chance to test these extensively.  Thanks
for your work debugging the failure on rx3600/rx6600; sounds like it was
a fairly generic bug.  I did briefly test on my rx2620 that had the SAL
errors before, they still occur :(  I'll try to debug this and maybe see
if I can get it to reproduce on another system since that led to some
useful hints with the previous issue.  I'm currently expecting that
we'll get these into the tree after the 3.2 release, assuming we work
out any remaining issues.  Thanks,

        Alex

On Tue, 2007-11-27 at 18:19 +0900, Simon Horman wrote:
> Its been about a month since I posted a fresh series, so here goes.
> Most of the changes are based on bugs reported by Alex Williamson
> and mostly fixed using an rx3600 that he has given me access too -
> very much appreciated, it would have been near impossible for me to
> debug the problems otherwise.
> 
> Specifically, the following problems have been addressed:
> 
> * Compile warnings.
>   - I have fixed a bunch of these that resulted from the patch
>     that creates the XEN_EFI_RR_ macros. I also fixed things
>     up so the #if !XEN case compiles, which was previously
>     completely broken. Alex, if there are other compile warnings
>     please let me know as I'm not noticing any.
> 
> * Fails to boot on rx3600
>   - This has been fixed by ensuring that the protection key is
>     set up correctly. Very simple but took a long time to find.
> 
> * Userspace segfaults - e.g. vi xen/arch/ia64/xen/ivt.S,
>                              make in the xen source tree
>   - This has been fixed by removing the asm cleanup patch that I provided
>     to consolidate some logic into branch_on_xen_memory. It was a dubious
>     change at best. Good riddance.
> 
> Other changes:
>   - Minnor whitespace / comment changes
> 
>   - Split asm code up into several small paches
>     + I found this the most convenient way to develop the code.
>       It allows me to pull out bits and push outher bits in to
>       see what breaks and what doesn't. I can consolodate if need be.
>     + This is why there are more patches this time around.
>       There is actually slightly less code.
> 
> Known problems:
> 
> * Fails to boot on rx2600
>   - Alex reported that take III of these patches dies in PAL calls.
>     I'm not sure if any of the above fixes resolve this problem.
>     But it would be worth testing.
> 
>   - I've been mainly concerntrating on first-kernel boot problems,
>     but it does seem that the following problems exist in relation
>     to kexec. They may or may not be related to these patches.
>     I mention them because the entire purpose of these patches
>     is for kexec.
> 
>     I have not spent much time on these problems, I only mention
>     them in case others see them.
> 
>     + Tiger2 kexec (xen->xen) hangs when booting the second kernel
>     + I am having trouble setting up a crashkernel region on the rx3600
>       Thus I have not been able to test kdump
>     + Kexec (xen->xen) seems to die in purgatory on the rx3600
> 
>     As always, everything is working just fine on my rx2620 :-)
> 
> Lastly for the sake of completeness, the description posted with
> the original series is below.
> 
-- 
Alex Williamson                             HP Open Source & Linux Org.


_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel