On Thu, Dec 27, 2012 at 07:06:13PM -0800, ebied...@xmission.com wrote:
Daniel Kiper daniel.ki...@oracle.com writes:
Daniel Kiper daniel.ki...@oracle.com writes:
Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
Linux infrastructure and require some support from
Daniel Kiper daniel.ki...@oracle.com writes:
Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
Linux infrastructure and require some support from firmware and/or
hypervisor.
To cope with that problem kexec firmware infrastructure was introduced.
It allows a
Daniel Kiper daniel.ki...@oracle.com writes:
Daniel Kiper daniel.ki...@oracle.com writes:
Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
Linux infrastructure and require some support from firmware and/or
hypervisor.
To cope with that problem kexec firmware
Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
Linux infrastructure and require some support from firmware and/or hypervisor.
To cope with that problem kexec firmware infrastructure was introduced.
It allows a developer to use all kexec/kdump features of given firmware
or
Daniel Kiper daniel.ki...@oracle.com writes:
Some kexec/kdump implementations (e.g. Xen PVOPS) could not use default
Linux infrastructure and require some support from firmware and/or hypervisor.
To cope with that problem kexec firmware infrastructure was introduced.
It allows a developer to
