From: Peter Maydell <peter.maydell@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: "Alexander Graf" <agraf@suse.de>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-arm@nongnu.org, "qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"Andreas Färber" <afaerber@suse.de>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 5/5] target-arm: support QMP dump-guest-memory
Date: Tue, 24 Nov 2015 21:08:29 +0000 [thread overview]
Message-ID: <CAFEAcA-E8hkOY05QVkZjzytpqYOYUJ2kDdCMNBjCaZ4A+6wo_g@mail.gmail.com> (raw)
In-Reply-To: <20151124205231.GA4383@hawk.localdomain>
On 24 November 2015 at 20:52, Andrew Jones <drjones@redhat.com> wrote:
>
> I've pulled a v2 together that I'll be testing and posting soon. Here's
> what I decided to do
>
> 1) Throw the fp registers in. Why not?
> 2) No linux-headers update, as we'd also need
> include/uapi/linux/elfcore.h and arch/arm/include/asm/user.h.
> However I've added comments stating where the structs come from.
> 3) Base the vmcore type on the guest kernel, i.e. use arm_el_is_aa64()
> and (env->cp15.sctlr_el[1] & SCTLR_EE). However,
> aarch64_write_elf64_note() will shoehorn 32-bit state into 64-bit
> elf notes when the current state is 32-bit. Those analyzing the
> dumps will need to look at the captured pstate to determine the
> endianness of the registers.
Not sure what you have in mind by "endianness of the registers" --
typically registers aren't thought of as having endianness.
Also, if we're currently executing a 32-bit guest when we take
the core dump, you probably need to call aarch64_sync_32_to_64()
somewhere.
thanks
-- PMM
next prev parent reply other threads:[~2015-11-24 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 14:53 [Qemu-devel] [PATCH 0/5] target-arm: enable qmp-dump-guest-memory Andrew Jones
2015-11-19 14:53 ` [Qemu-devel] [PATCH 1/5] qapi-schema: dump-guest-memory: Improve text Andrew Jones
2015-11-19 15:22 ` Eric Blake
2015-11-19 14:53 ` [Qemu-devel] [PATCH 2/5] dump: qemunotes aren't commonly needed Andrew Jones
2015-11-20 18:20 ` Peter Maydell
2015-11-19 14:53 ` [Qemu-devel] [PATCH 3/5] dump: allow target to set the page size Andrew Jones
2015-11-19 14:53 ` [Qemu-devel] [PATCH 4/5] dump: allow target to set the physical base Andrew Jones
2015-11-19 14:53 ` [Qemu-devel] [PATCH 5/5] target-arm: support QMP dump-guest-memory Andrew Jones
2015-11-20 18:19 ` Peter Maydell
2015-11-20 21:41 ` Andrew Jones
2015-11-21 15:05 ` Andrew Jones
2015-11-24 20:52 ` Andrew Jones
2015-11-24 21:08 ` Peter Maydell [this message]
2015-11-24 21:45 ` Andrew Jones
2015-11-24 22:01 ` Peter Maydell
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=CAFEAcA-E8hkOY05QVkZjzytpqYOYUJ2kDdCMNBjCaZ4A+6wo_g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=rth@twiddle.net \
/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).