From: Laszlo Ersek <lersek@redhat.com>
To: Phi Debian <phi.debian@gmail.com>
Cc: Dave Anderson <anderson@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] dump-guest-memory enhancement.
Date: Mon, 11 Nov 2013 01:50:09 +0100 [thread overview]
Message-ID: <528029C1.6040800@redhat.com> (raw)
In-Reply-To: <CAJOr74jtKZBJOTESjdU+0pmkwY=rC_3_e_-aGaVEfVQWcuoNQg@mail.gmail.com>
On 11/10/13 10:10, Phi Debian wrote:
> Hi All,
>
> I implemented guest-dump-memory for arm32, and bumped in something
> strange, the PT_LOADs generated from dump.c are not target page
> aligned. There are some advantage to get PT_LOAD aligned.
>
> This mail is to ask advise about patch I could submit later if wanted.
>
> Would it be desirable to get the PT_LOAD aligned on target page size
> always, for all arch ?
Can you please explain the problem in more detail? Preferably
illustrated by "readelf" output.
Is it about the placement of the PT_LOAD entries in the core file (eg.
their distance of the beginning of the file, or some such), or about the
contents of the PT_LOAD entries? (Ie. the target-phys ranges they
describe and where those are located in the core file.)
Thanks
Laszlo
> If so I could fix dump.c, but may be people using dump-guest-memory on
> existing current implementation may object, dunno if some of there
> tools (debuggers) are dependent of the non aligned current setup (gdb
> would nt complain)
>
> If not wanted for existing arch (s390, ppc, i386), may be I could do
> it for arm only.
>
> Or ultimatly may be this is not wanted at all, in this case I keep my
> dumper for myself :)
>
> Cheers,
> Phi
>
next prev parent reply other threads:[~2013-11-11 0:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-10 9:10 [Qemu-devel] dump-guest-memory enhancement Phi Debian
2013-11-11 0:50 ` Laszlo Ersek [this message]
2013-11-11 3:28 ` Phi Debian
2013-11-11 19:38 ` Laszlo Ersek
2013-11-11 20:02 ` Phi Debian
2013-11-12 14:23 ` Dave Anderson
2013-11-11 21:28 ` 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=528029C1.6040800@redhat.com \
--to=lersek@redhat.com \
--cc=anderson@redhat.com \
--cc=phi.debian@gmail.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).