From: Greg Kurz <gkurz@linux.vnet.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Jens Freimann" <jfrei@linux.vnet.ibm.com>,
"Andreas Färber" <afaerber@suse.de>,
qemu-devel@nongnu.org, "Anthony Liguori" <aliguori@amazon.com>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH] include/qom/cpu.h: Add missing documentation for some CPUClass methods
Date: Mon, 5 Jan 2015 20:54:51 +0100 [thread overview]
Message-ID: <20150105205451.4d6a0991@bahia.local> (raw)
In-Reply-To: <1420467812-31917-1-git-send-email-peter.maydell@linaro.org>
On Mon, 5 Jan 2015 14:23:32 +0000
Peter Maydell <peter.maydell@linaro.org> wrote:
> The CPUClass QOM methods virtio_is_big_endian, write_elf{32,64}_note
> and write_elf{32,64}_qemunote were added without any description
> being added to the doc comment. Correct this omission.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
Thanks for this accurate description of virtio_is_big_endian.
Acked-by: Greg Kurz <gkurz@linux.vnet.ibm.com>
> More informative phrasings for the elf note callbacks welcome...
>
> include/qom/cpu.h | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/include/qom/cpu.h b/include/qom/cpu.h
> index 2098f1c..f2d7de1 100644
> --- a/include/qom/cpu.h
> +++ b/include/qom/cpu.h
> @@ -82,6 +82,10 @@ struct TranslationBlock;
> * @do_unassigned_access: Callback for unassigned access handling.
> * @do_unaligned_access: Callback for unaligned access handling, if
> * the target defines #ALIGNED_ONLY.
> + * @virtio_is_big_endian: Callback to return true if a CPU which supports
> + * runtime configurable endianness is currently big-endian. Non-configurable
> + * CPUs can use the default implementation of this method. This method should
> + * not be used by any callers other than the pre-1.0 virtio devices.
> * @memory_rw_debug: Callback for GDB memory access.
> * @dump_state: Callback for dumping state.
> * @dump_statistics: Callback for dumping statistics.
> @@ -96,6 +100,14 @@ struct TranslationBlock;
> * @gdb_read_register: Callback for letting GDB read a register.
> * @gdb_write_register: Callback for letting GDB write a register.
> * @debug_excp_handler: Callback for handling debug exceptions.
> + * @write_elf64_note: Callback for writing a CPU-specific ELF note to a
> + * 64-bit VM coredump.
> + * @write_elf32_qemunote: Callback for writing a CPU- and QEMU-specific ELF
> + * note to a 32 bit VM coredump.
> + * @write_elf32_note: Callback for writing a CPU-specific ELF note to a
> + * 32-bit VM coredump.
> + * @write_elf32_qemunote: Callback for writing a CPU- and QEMU-specific ELF
> + * note to a 32 bit VM coredump.
> * @vmsd: State description for migration.
> * @gdb_num_core_regs: Number of core registers accessible to GDB.
> * @gdb_core_xml_file: File name for core registers GDB XML description.
next prev parent reply other threads:[~2015-01-05 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 14:23 [Qemu-devel] [PATCH] include/qom/cpu.h: Add missing documentation for some CPUClass methods Peter Maydell
2015-01-05 19:54 ` Greg Kurz [this message]
2015-01-07 16:16 ` Andreas Färber
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=20150105205451.4d6a0991@bahia.local \
--to=gkurz@linux.vnet.ibm.com \
--cc=afaerber@suse.de \
--cc=aliguori@amazon.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--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).