diff options
| author | Alex Williamson <alex.williamson@hp.com> | 2007-10-22 12:26:53 -0600 |
|---|---|---|
| committer | Alex Williamson <alex.williamson@hp.com> | 2007-10-22 12:26:53 -0600 |
| commit | 34070c37f55e7b04f2dc9d6e9f71ea238d8131fa (patch) | |
| tree | 71b986b26d1bb7d1922c6d76e8474c70d7231e3a /tools/libxc/xc_core.c | |
| parent | de5d56f31dd18fde2297e6f7ea1a1bc2e809ffe5 (diff) | |
| download | xen-34070c37f55e7b04f2dc9d6e9f71ea238d8131fa.tar.gz xen-34070c37f55e7b04f2dc9d6e9f71ea238d8131fa.tar.bz2 xen-34070c37f55e7b04f2dc9d6e9f71ea238d8131fa.zip | |
[IA64] Don't share privregs with hvm domain
Don't share privregs with hvm domain and twist IA64 xen dump core format
slightly. Xen shares privregs pages with IA64 HVM domain for xm dump-core
to dump the pages. However sharing the page allows hvm guest domain
peek/destroy the page contents that might cause xen crash. And the xen
dump core file doesn't need privregs page because cpu context should be
obtained from vcpu context in case of IA64 HVM domain.
Although this patch modify xen dump core format, current crash utility
(at least crash 4.0-4.7) doesn't look into .xen_ia64_mmapped_regs section
and I don't know any other tools to understand xen dump core file.
So this format modification doesn't cause incompatibility issue.
Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
Diffstat (limited to 'tools/libxc/xc_core.c')
| -rw-r--r-- | tools/libxc/xc_core.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/tools/libxc/xc_core.c b/tools/libxc/xc_core.c index a939e95c75..edcf67cfc0 100644 --- a/tools/libxc/xc_core.c +++ b/tools/libxc/xc_core.c @@ -32,7 +32,7 @@ * |.xen_prstatus | * | vcpu_guest_context_t[nr_vcpus] | * +--------------------------------------------------------+ - * |.xen_ia64_mmapped_regs if ia64 | + * |.xen_ia64_mmapped_regs if ia64 pv | * | mmapped_regs_t[nr_vcpus] | * +--------------------------------------------------------+ * |.xen_shared_info if possible | |