aboutsummaryrefslogtreecommitdiffstats
path: root/tools/debugger/xenitp/dis-asm.h
diff options
context:
space:
mode:
authorJan Beulich <jbeulich@suse.com>2012-09-12 10:19:34 +0200
committerJan Beulich <jbeulich@suse.com>2012-09-12 10:19:34 +0200
commit81da4016bfeb5bde06b79004bf5df8738259b1a3 (patch)
tree5a262e900cfefcba62493e43395fd66935c7a909 /tools/debugger/xenitp/dis-asm.h
parent7aa9625cc4b549a6316b43c5f07cc2dec1d7a8ce (diff)
downloadxen-81da4016bfeb5bde06b79004bf5df8738259b1a3.tar.gz
xen-81da4016bfeb5bde06b79004bf5df8738259b1a3.tar.bz2
xen-81da4016bfeb5bde06b79004bf5df8738259b1a3.zip
x86-64/EFI: allow chaining of config files
Namely when making use the CONFIG_XEN_COMPAT_* options in the legacy Linux kernels, newer kernels may not be compatible with older hypervisors, so trying to boot such a combination makes little sense. Booting older kernels on newer hypervisors, however, has to always work. With the way xen.efi looks for its configuration file, allowing individual configuration files to refer only to compatible kernels, and referring from an older- to a newer-hypervisor one (the kernels of which will, as said, necessarily be compatible with the older hypervisor) allows to greatly reduce redundancy at least in development environments where one frequently wants multiple hypervisors and kernles to be installed in parallel. Signed-off-by: Jan Beulich <jbeulich@suse.com> Acked-by: Keir Fraser <keir@xen.org>
Diffstat (limited to 'tools/debugger/xenitp/dis-asm.h')
0 files changed, 0 insertions, 0 deletions