From: Laszlo Ersek <lersek@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: anderson@redhat.com, qiaonuohan@cn.fujitsu.com
Subject: Re: [Qemu-devel] [PATCH v2 1/4] dump: add DumpInfo structure
Date: Thu, 1 Jun 2017 20:06:38 +0200 [thread overview]
Message-ID: <465a7b69-a3c0-1492-8e30-c562a76cd65a@redhat.com> (raw)
In-Reply-To: <20170601130325.6433-2-marcandre.lureau@redhat.com>
On 06/01/17 15:03, Marc-André Lureau wrote:
> One way or another, the guest could communicate various dump info (via
> guest agent or vmcoreinfo device) and populate that structure. It can
> then be used to augment the dump with various details, as done in the
> following patch.
>
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> include/sysemu/dump-info.h | 18 ++++++++++++++++++
> dump.c | 3 +++
> 2 files changed, 21 insertions(+)
> create mode 100644 include/sysemu/dump-info.h
>
> diff --git a/include/sysemu/dump-info.h b/include/sysemu/dump-info.h
> new file mode 100644
> index 0000000000..d2378e15e2
> --- /dev/null
> +++ b/include/sysemu/dump-info.h
> @@ -0,0 +1,18 @@
> +#ifndef DUMP_INFO_H
> +#define DUMP_INFO_H
> +
> +typedef struct DumpInfo {
> + bool received;
> + /* kernel base address */
> + bool has_phys_base;
> + uint64_t phys_base;
> + /* "_text" symbol location */
> + bool has_text;
> + uint64_t text;
> + /* the content of /sys/kernel/vmcoreinfo on Linux */
> + char *vmcoreinfo;
> +} DumpInfo;
> +
> +extern DumpInfo dump_info;
> +
> +#endif /* DUMP_INFO_H */
> diff --git a/dump.c b/dump.c
> index d9090a24cc..bdf3270f02 100644
> --- a/dump.c
> +++ b/dump.c
> @@ -20,6 +20,7 @@
> #include "monitor/monitor.h"
> #include "sysemu/kvm.h"
> #include "sysemu/dump.h"
> +#include "sysemu/dump-info.h"
> #include "sysemu/sysemu.h"
> #include "sysemu/memory_mapping.h"
> #include "sysemu/cpus.h"
> @@ -38,6 +39,8 @@
> #define ELF_MACHINE_UNAME "Unknown"
> #endif
>
> +DumpInfo dump_info = { 0, };
> +
> uint16_t cpu_to_dump16(DumpState *s, uint16_t val)
> {
> if (s->dump_info.d_endian == ELFDATA2LSB) {
>
Can you please spell out, in the commit message, the reason for
introducing a new header file? (I suspect your reason, but it should be
documented explicitly.)
Thanks
Laszlo
next prev parent reply other threads:[~2017-06-01 18:06 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 13:03 [Qemu-devel] [PATCH v2 0/4] dump: add vmcoreinfo note Marc-André Lureau
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 1/4] dump: add DumpInfo structure Marc-André Lureau
2017-06-01 18:06 ` Laszlo Ersek [this message]
2017-06-01 18:18 ` Eric Blake
2017-06-02 9:46 ` Marc-André Lureau
2017-06-02 9:55 ` Marc-André Lureau
2017-06-02 22:49 ` Laszlo Ersek
2017-06-04 15:56 ` Zhang Chen
2017-06-06 18:19 ` Laszlo Ersek
2017-06-05 7:24 ` Andrew Jones
2017-06-06 2:11 ` Peter Xu
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 2/4] dump: add vmcoreinfo ELF note Marc-André Lureau
2017-06-01 18:38 ` Laszlo Ersek
2017-06-02 11:13 ` Marc-André Lureau
2017-06-06 14:21 ` Laszlo Ersek
2017-06-29 12:47 ` Marc-André Lureau
2017-06-05 8:04 ` Andrew Jones
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 3/4] kdump: add vmcoreinfo Marc-André Lureau
2017-06-05 8:07 ` Andrew Jones
2017-06-01 13:03 ` [Qemu-devel] [PATCH v2 4/4] scripts/dump-guest-memory.py: " Marc-André Lureau
2017-06-01 13:46 ` [Qemu-devel] [PATCH v2 0/4] dump: add vmcoreinfo note no-reply
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=465a7b69-a3c0-1492-8e30-c562a76cd65a@redhat.com \
--to=lersek@redhat.com \
--cc=anderson@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qiaonuohan@cn.fujitsu.com \
/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).