Re: [Xen-ia64-devel] EFI Mapping Windows Install Crash Bug

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

On Tue, Jul 22, 2008 at 01:07:20PM +1000, Simon Horman wrote:
> On Mon, Jul 14, 2008 at 12:22:21PM +0900, Isaku Yamahata wrote:
> > Hi Simon-san.
> > 
> > I attached the four ptaches, please review and integrate
> > them into your patchset if appropriate.
> > Although I haven't splited them up, I'm posting them because
> > I think they would help to show the issues.
> > 
> >   remove-warning-and-vpd-itr-fix.patch
> >   cleanup-pal-vaddr.patch
> >   dont-map-pal-code.patch
> >   purge-pal-code-after-firmware-call.patch
> > 
> > 
> > I reviewed the kexec patches and tried on my testing machine.
> > Xen/IA64 VMM failed to boot. initial boot. non-kexec boot.
> > I created some patches to fix it, and with those patches
> > Xen/IA64 can boot. (I'm going to test kexec...)
> > 
> > The main issue is 
> >   The rule how to pin down PAL code was changed.
> >   So far PAL code was always pinned down by
> >   itr[IA64_TR_PALCODE], however it has been changed
> >   such that PAL code is pinned down right before
> >   calling firmware by setn_one_rr_efi() with region 7.
> >   But without the attached patch, PAL code is wrongly always
> >   pinned down to wrong address calculated by efi_get_pal_addr()
> > 
> >   The attached patch fixes the calculation in efi_get_pal_addr()
> >   and makes functions which switch rr7 not pin down PAL code.
> 
> Hi Yamahata-san,
> 
> Sorry, I didn't see these patches until just now.
> I will review them and get back to you ASAP.

Hi.
It's unnecessary. All of them had already been integrated into 
your patch set with the following spin of patches.

-- 
yamahata

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