OK, I finally got these all downloaded.  However, the xen-syms
binary in the "sample-1" directory has no debug data:

# file xen-syms-2.6.18-8.el5
xen-syms-2.6.18-8.el5: ELF 64-bit LSB executable, IA-64, version
1 (SYSV), statically linked, stripped
#

And I see that check_netdump_xen() is only called if the
netdump (?) vmcore is used, since it needs the --p2m_mfn
argument.  I have no idea where check_kdump_xen() would
apply?

In any case, I really prefer not to support whatever that
first "hard assist dump. netdump style ELF" vmcore file.
(What is that???)

I don't see why the support for dom0 ia64 kdumps should
be any different than for x86 and x86_64, both of which
have XEN_ELFNOTE_CRASH_INFO notes containing the p2m mfn
value.
Therefore, the check_netdump_xen() and check_kdump_xen()
can be thrown out, and all that is really required is the
implementation of ia64_xen_kdump_p2m_create() for the vmlinux
side.  But it will still need a fix to deal with that
over-sized (?) 512k p2m_frame list.  Can you look into fixing
that?

Also, I don't quite understand the changes to xen_kdump_p2m().
The first (generic) part is probably a safe thing to do:

+       if (mfn_idx >= xkd->p2m_frames)
+              
return P2M_FAILURE;

But if the above code is put into place, how would it
be possible for the resultant mfn_frame to be 0?

+ #ifdef IA64
+         if (mfn_frame
== 0)
+                
return P2M_FAILURE;
+ #endif

And I don't understand this part at all:

+ #ifdef IA64
+         if (!(*mfnptr
& 0x1))
+                
return P2M_FAILURE;
+         paddr = *mfnptr
& _PFN_MASK;
+ #else
+         paddr = (physaddr_t)PTOB((ulonglong)(*mfnptr));
+ #endif

Although, after putting in a debug printf of what the mfns
actually look like on an ia64, I guess I see why it's
necessary.

On x86 and x86_64, the mfnptr points to a simple mfn value.

But on the ia64, I see mfns that look like 81000007bf3c761,
where the "1-bit" is always set.  And you don't shift the
mfn value like x86/x86_64 do.  Can you help me understand
the format of the ia64 mfns?  In other words, what part of
a
value such as 81000007bf3c761 is the actual mfn?  Are there
page flags or something in the lower bits of the number?

Thanks,
  Dave