[Xen-devel] [PATCH v2 01/11] kexec: introduce kexec_ops struct
daniel.kiper at oracle.com
Fri Nov 23 06:13:08 EST 2012
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.cooper3 at 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.
More information about the kexec