qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Wen Congyang <wency@cn.fujitsu.com>
To: qemu-devel <qemu-devel@nongnu.org>,
	Jan Kiszka <jan.kiszka@siemens.com>,
	Dave Anderson <anderson@redhat.com>,
	HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Subject: [Qemu-devel] [RFC][PATCH 07/14 v4] target-i386: add API to get dump info
Date: Wed, 04 Jan 2012 14:10:04 +0800	[thread overview]
Message-ID: <4F03ED3C.2010607@cn.fujitsu.com> (raw)
In-Reply-To: <4F03E735.2050804@cn.fujitsu.com>

Dump info contains: endian, class and architecture. The next
patch will use these information to create vmcore.

Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
---
 cpu-all.h               |    3 +++
 dump.h                  |   10 ++++++++++
 target-i386/arch-dump.c |   34 ++++++++++++++++++++++++++++++++++
 3 files changed, 47 insertions(+), 0 deletions(-)
 create mode 100644 dump.h

diff --git a/cpu-all.h b/cpu-all.h
index 684d7ef..199b756 100644
--- a/cpu-all.h
+++ b/cpu-all.h
@@ -23,6 +23,7 @@
 #include "qemu-tls.h"
 #include "cpu-common.h"
 #include "memory_mapping.h"
+#include "dump.h"
 
 /* some important defines:
  *
@@ -583,11 +584,13 @@ int cpu_write_elf64_note(int fd, CPUState *env, int cpuid,
 int cpu_write_elf32_note(int fd, CPUState *env, int cpuid,
                          target_phys_addr_t *offset);
 int cpu_add_extra_memory_mapping(MemoryMappingList *list);
+int cpu_get_dump_info(ArchDumpInfo *info);
 #else
 #define cpu_get_memory_mapping(list, env)
 #define cpu_write_elf64_note(fd, env, cpuid, offset) ({ -1; })
 #define cpu_write_elf32_note(fd, env, cpuid, offset) ({ -1; })
 #define cpu_add_extra_memory_mapping(list) ({ 0; })
+#define cpu_get_dump_info(info) ({ -1; })
 #endif
 
 #endif /* CPU_ALL_H */
diff --git a/dump.h b/dump.h
new file mode 100644
index 0000000..a36468b
--- /dev/null
+++ b/dump.h
@@ -0,0 +1,10 @@
+#ifndef DUMP_H
+#define DUMP_H
+
+typedef struct ArchDumpInfo {
+    int d_machine;  /* Architecture */
+    int d_endian;   /* ELFDATA2LSB or ELFDATA2MSB */
+    int d_class;    /* ELFCLASS32 or ELFCLASS64 */
+} ArchDumpInfo;
+
+#endif
diff --git a/target-i386/arch-dump.c b/target-i386/arch-dump.c
index d96f6ae..92a53bc 100644
--- a/target-i386/arch-dump.c
+++ b/target-i386/arch-dump.c
@@ -15,6 +15,7 @@
 
 #include "cpu.h"
 #include "cpu-all.h"
+#include "dump.h"
 #include "monitor.h"
 
 /* PAE Paging or IA-32e Paging */
@@ -538,3 +539,36 @@ int cpu_add_extra_memory_mapping(MemoryMappingList *list)
 #endif
     return 0;
 }
+
+int cpu_get_dump_info(ArchDumpInfo *info)
+{
+    bool lma = false;
+    RAMBlock *block;
+
+#ifdef TARGET_X86_64
+    lma = !!(first_cpu->hflags & HF_LMA_MASK);
+#endif
+
+    if (lma) {
+        info->d_machine = EM_X86_64;
+    } else {
+        info->d_machine = EM_386;
+    }
+    info->d_endian = ELFDATA2LSB;
+
+    if (lma) {
+        info->d_class = ELFCLASS64;
+    } else {
+        info->d_class = ELFCLASS32;
+    }
+
+    QLIST_FOREACH(block, &ram_list.blocks, next) {
+        if (!lma && (block->offset + block->length > UINT_MAX)) {
+            /* The memory size is greater than 4G */
+            info->d_class = ELFCLASS32;
+            break;
+        }
+    }
+
+    return 0;
+}
-- 
1.7.1

  parent reply	other threads:[~2012-01-04  6:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  5:44 [Qemu-devel] [RFC][PATCT 0/14 v4] dump memory when host pci device is used by guest Wen Congyang
2012-01-04  6:04 ` [Qemu-devel] [RFC][PATCH 01/14 v4] Add API to create memory mapping list Wen Congyang
2012-01-04  6:05 ` [Qemu-devel] [RFC][PATCH 02/14 v4] Add API to check whether a physical address is I/O address Wen Congyang
2012-01-04  6:06 ` [Qemu-devel] [RFC][PATCH 03/14 v4] target-i386: implement cpu_get_memory_mapping() Wen Congyang
2012-01-04  6:07 ` [Qemu-devel] [RFC][PATCH 04/14 v4] Add API to get memory mapping Wen Congyang
2012-01-04  6:08 ` [Qemu-devel] [RFC][PATCH 05/14 v4] target-i386: Add API to write elf notes to core file Wen Congyang
2012-01-04  6:09 ` [Qemu-devel] [RFC][PATCH 06/14 v4] target-i386: Add API to add extra memory mapping Wen Congyang
2012-01-04  6:10 ` Wen Congyang [this message]
2012-01-04  6:11 ` [Qemu-devel] [RFC][PATCH 08/14 v4] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2012-01-10 13:30   ` Luiz Capitulino
2012-01-11  0:59     ` Wen Congyang
2012-01-12 13:49       ` Luiz Capitulino
2012-01-13  8:35         ` Wen Congyang
2012-01-04  6:12 ` [Qemu-devel] [RFC][PATCH 09/14 v4] run dump at the background Wen Congyang
2012-01-04  6:13 ` [Qemu-devel] [RFC][PATCH 10/14 v4] support detached dump Wen Congyang
2012-01-04  6:14 ` [Qemu-devel] [RFC][PATCH 11/14 v4] support to cancel the current dumping Wen Congyang
2012-01-04  6:15 ` [Qemu-devel] [RFC][PATCH 12/14 v4] support to set dumping speed Wen Congyang
2012-01-04  6:16 ` [Qemu-devel] [RFC][PATCH 13/14 v4] support to query dumping status Wen Congyang
2012-01-04  6:17 ` [Qemu-devel] [RFC][PATCH 14/14 v4] auto cancel dumping after vm state is changed to run Wen Congyang
2012-01-10  7:44 ` [Qemu-devel] [RFC][PATCT 0/14 v4] dump memory when host pci device is used by guest Wen Congyang
2012-01-10  9:41   ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F03ED3C.2010607@cn.fujitsu.com \
    --to=wency@cn.fujitsu.com \
    --cc=anderson@redhat.com \
    --cc=d.hatayama@jp.fujitsu.com \
    --cc=jan.kiszka@siemens.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).