Thread (1 message) flat view 1 message, 1 author, 2012-11-23

Re: [Xen-devel] [PATCH v2 01/11] kexec: introduce kexec_ops struct

From: Daniel Kiper <hidden>
Date: 2012-11-23 11:14:10
Also in: kexec, lkml, xen-devel

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:
quoted
On Fri, Nov 23, 2012 at 09:53:37AM +0000, Jan Beulich wrote:
quoted
quoted
quoted
quoted
On 23.11.12 at 02:56, Andrew Cooper [off-list ref] 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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help