From: Wen Congyang <wency@cn.fujitsu.com>
To: HATAYAMA Daisuke <d.hatayama@jp.fujitsu.com>
Cc: jan.kiszka@siemens.com, anderson@redhat.com,
qemu-devel@nongnu.org, eblake@redhat.com, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [RFC][PATCH 08/14 v9] target-i386: Add API to write cpu status to core file
Date: Fri, 16 Mar 2012 14:50:06 +0800 [thread overview]
Message-ID: <4F62E29E.7000904@cn.fujitsu.com> (raw)
In-Reply-To: <20120316.104836.424250617.d.hatayama@jp.fujitsu.com>
At 03/16/2012 09:48 AM, HATAYAMA Daisuke Wrote:
> From: Wen Congyang <wency@cn.fujitsu.com>
> Subject: [RFC][PATCH 08/14 v9] target-i386: Add API to write cpu status to core file
> Date: Wed, 14 Mar 2012 10:09:26 +0800
>
>> + memset(note, 0, note_size);
>> + if (type == 0) {
>> + note32 = note;
>> + note32->n_namesz = cpu_to_le32(name_size);
>> + note32->n_descsz = cpu_to_le32(descsz);
>> + note32->n_type = 0;
>> + } else {
>> + note64 = note;
>> + note64->n_namesz = cpu_to_le32(name_size);
>> + note64->n_descsz = cpu_to_le32(descsz);
>> + note64->n_type = 0;
>> + }
>
> Why not give new type for this note information an explicit name?
> Like NT_QEMUCPUSTATE? There might be another type in the future. This
> way there's also a merit that we can know all the existing notes
> relevant to qemu dump by looking at the names in a header file.
Hmm, how to add a new type? Does someont manage this?
Thanks
Wen Congyang
>
> Thanks.
> HATAYAMA, Daisuke
>
>
next prev parent reply other threads:[~2012-03-16 6:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-14 2:03 [Qemu-devel] [RFC][PATCH 00/14 v9] introducing a new, dedicated memory dump mechanism Wen Congyang
2012-03-14 2:05 ` [Qemu-devel] [RFC][PATCH 01/14 v9] Add API to create memory mapping list Wen Congyang
2012-03-14 2:06 ` [Qemu-devel] [RFC][PATCH 02/14 v9] Add API to check whether a physical address is I/O address Wen Congyang
2012-03-14 9:18 ` [Qemu-devel] [RESEND][PATCH " Wen Congyang
2012-03-14 2:06 ` [Qemu-devel] [RFC][PATCH 03/14 v9] implement cpu_get_memory_mapping() Wen Congyang
2012-03-14 2:07 ` [Qemu-devel] [RFC][PATCH 04/14 v9] Add API to check whether paging mode is enabled Wen Congyang
2012-03-14 2:07 ` [Qemu-devel] [RFC][PATCH 05/14 v9] Add API to get memory mapping Wen Congyang
2012-03-16 3:52 ` HATAYAMA Daisuke
2012-03-16 6:50 ` Wen Congyang
2012-03-16 6:38 ` HATAYAMA Daisuke
2012-03-16 6:59 ` Wen Congyang
2012-03-14 2:08 ` [Qemu-devel] [RFC][PATCH 06/14 v9] Add API to get memory mapping without do paging Wen Congyang
2012-03-14 2:08 ` [Qemu-devel] [RFC][PATCH 07/14 v9] target-i386: Add API to write elf notes to core file Wen Congyang
2012-03-16 1:17 ` HATAYAMA Daisuke
2012-03-14 2:09 ` [Qemu-devel] [RFC][PATCH 08/14 v9] target-i386: Add API to write cpu status " Wen Congyang
2012-03-16 1:48 ` HATAYAMA Daisuke
2012-03-16 6:50 ` Wen Congyang [this message]
2012-03-19 1:09 ` HATAYAMA Daisuke
2012-03-14 2:09 ` [Qemu-devel] [RFC][PATCH 09/14 v9] target-i386: add API to get dump info Wen Congyang
2012-03-14 2:10 ` [Qemu-devel] [RFC][PATCH 10/14 v9] make gdb_id() generally avialable Wen Congyang
2012-03-14 2:11 ` [Qemu-devel] [RFC][PATCH 11/14 v9] introduce a new monitor command 'dump' to dump guest's memory Wen Congyang
2012-03-14 17:18 ` Luiz Capitulino
2012-03-15 2:29 ` Wen Congyang
2012-03-15 14:25 ` Luiz Capitulino
2012-03-16 10:13 ` Wen Congyang
2012-03-19 2:28 ` Wen Congyang
2012-03-19 8:31 ` Wen Congyang
2012-03-19 13:16 ` Luiz Capitulino
2012-03-16 3:23 ` HATAYAMA Daisuke
2012-03-16 6:41 ` Wen Congyang
2012-03-14 2:12 ` [Qemu-devel] [RFC][PATCH 12/14 v9] support to cancel the current dumping Wen Congyang
2012-03-14 17:19 ` Luiz Capitulino
2012-03-14 2:13 ` [Qemu-devel] [RFC][PATCH 13/14 v9] support to query dumping status Wen Congyang
2012-03-14 17:19 ` Luiz Capitulino
2012-03-14 2:13 ` [Qemu-devel] [RFC][PATCH 14/14 v9] allow user to dump a fraction of the memory Wen Congyang
2012-03-14 17:20 ` Luiz Capitulino
2012-03-14 17:26 ` [Qemu-devel] [RFC][PATCH 00/14 v9] introducing a new, dedicated memory dump mechanism Luiz Capitulino
2012-03-14 17:37 ` Eric Blake
2012-03-14 17:49 ` Anthony Liguori
2012-03-14 18:03 ` Luiz Capitulino
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=4F62E29E.7000904@cn.fujitsu.com \
--to=wency@cn.fujitsu.com \
--cc=anderson@redhat.com \
--cc=d.hatayama@jp.fujitsu.com \
--cc=eblake@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lcapitulino@redhat.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).