ia64/xen-unstable

changeset 19049:04f913ab2049

dump-core: update the documentation

Signed-off-by: Isaku Yamahata <yamahata@valinux.co.jp>
author Keir Fraser <keir.fraser@citrix.com>
date Thu Jan 15 12:40:48 2009 +0000 (2009-01-15)
parents e98032a016d6
children d84504432e61
files docs/misc/dump-core-format.txt
line diff
     1.1 --- a/docs/misc/dump-core-format.txt	Thu Jan 15 12:39:59 2009 +0000
     1.2 +++ b/docs/misc/dump-core-format.txt	Thu Jan 15 12:40:48 2009 +0000
     1.3 @@ -30,8 +30,13 @@ The elf header members are set as follow
     1.4          e_ident[EI_OSABI] = ELFOSABI_SYSV = 0
     1.5          e_type = ET_CORE = 4
     1.6  ELFCLASS64 is always used independent of architecture.
     1.7 -e_ident[EI_DATA] and e_flags are set according to the dumping system's
     1.8 -architecture. Other members are set as usual.
     1.9 +e_ident[EI_DATA] is set as follows
    1.10 +  For x86 PV domain case, it is set according to the guest configuration
    1.11 +  (i.e. if guest is 32bit it is set to EM_386 even when the dom0 is 64 bit.)
    1.12 +  For other domain case (x86 HVM domain case and ia64 domain case),
    1.13 +  it is set according to the dumping system's architecture.
    1.14 +e_flags is set according to the dumping system's architecture.
    1.15 +Other members are set as usual.
    1.16  
    1.17  Sections
    1.18  --------
    1.19 @@ -241,3 +246,7 @@ Currently only (major, minor) = (0, 1) i
    1.20    The format version isn't bumped because analysis tools can distinguish it.
    1.21  - .xen_ia64_mapped_regs section was made only for ia64 PV domain.
    1.22    In case of IA64 HVM domain, this section doesn't exist.
    1.23 +- elf header e_ident[EI_DATA]
    1.24 +  On x86 PV domain case, it is set according to the guest configuration.
    1.25 +  I.e. 32-on-64 case, the file will be set EM_386 instead of EM_X86_64.
    1.26 +  This is the same as 32-on-32 case, so there is no impact on analysis tools.