On Fri, Nov 23, 2012 at 10:51:08AM +0000, Ian Campbell wrote: > On Fri, 2012-11-23 at 10:37 +0000, Daniel Kiper wrote: > > On Fri, Nov 23, 2012 at 09:53:37AM +0000, Jan Beulich wrote: > > > >>> On 23.11.12 at 02:56, Andrew Cooper <andrew.coop...@citrix.com> wrote: > > > > The crash region (as specified by crashkernel= on the Xen command line) > > > > is isolated from dom0. > > > >[...] > > > > > > But all of this _could_ be done completely independent of the > > > Dom0 kernel's kexec infrastructure (i.e. fully from user space, > > > invoking the necessary hypercalls through the privcmd driver). > > > > No, this is impossible. kexec/kdump image lives in dom0 kernel memory > > until execution. > > Are you sure? I could have sworn they lived in the hypervisor owned > memory set aside by the crashkernel= parameter as Andy suggested.
I am sure. It is moved to final resting place when relocate_kernel() is called by hypervisor. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
