286
286
# makedumpfile \-E \-X /proc/vmcore dumpfile
289
\fB\-\-message-level\fR \fImessage_level\fR
290
Specify the message types.
292
diff -puN makedumpfile.org/makedumpfile.c makedumpfile/makedumpfile.c
293
--- makedumpfile.org/makedumpfile.c 2008-04-09 15:48:19.000000000 +0900
294
+++ makedumpfile/makedumpfile.c 2008-04-09 15:48:34.000000000 +0900
295
@@ -429,6 +429,10 @@ print_usage()
296
MSG(" [--xen-vmcoreinfo VMCOREINFO]:\n");
297
MSG(" Specify the VMCOREINFO of Xen to analyze Xen's memory usage.\n");
289
\fB\-\-xen_phys_start\fR \fIxen_phys_start_address\fR
290
This option is only for x86_64.
291
Specify the \fIxen_phys_start_address\fR, if the xen code/data is relocatable
292
and \fIVMCORE\fR does not contain \fIxen_phys_start_address\fR in the CRASHINFO.
293
\fIxen_phys_start_address\fR can be token from the line of "Hypervisor code
294
and data" in /proc/iomem. For example, specify 0xcee00000 as \fIxen_phys_start_address\fR
295
if /proc/iomem is the following:
296
-------------------------------------------------------
299
cee00000-cfd99999 : Hypervisor code and data
301
-------------------------------------------------------
306
# makedumpfile \-E \-X \-\-xen_phys_start 0xcee00000 /proc/vmcore dumpfile
299
309
\fB\-\-message-level\fR \fImessage_level\fR
300
310
Specify the message types.
345
355
31 | X | X | X | X | X
358
\fB\-\-vtop\fR \fIvirtual_address\fR
359
This option is useful, when user debugs the translation problem
360
of virtual address. If specifing \fIvirtual_address\fR, its physical
361
address is printed. It makes debugging easy by comparing the
362
output of this option with the one of "vtop" subcommand of the
364
"--vtop" option only prints the translation output, and it does
365
not affect the dumpfile creation.
349
369
Print debugging message.