From: Avi Kivity <avi@redhat.com>
To: Matteo Signorini <signorinimatteo@gmail.com>
Cc: kvm@vger.kernel.org
Subject: Re: physical memory dump problem
Date: Tue, 02 Jun 2009 12:55:40 +0300 [thread overview]
Message-ID: <4A24F71C.7080005@redhat.com> (raw)
In-Reply-To: <bdf5bab30906020231p625a0e1bh76f7ba08a1e2dd3c@mail.gmail.com>
Matteo Signorini wrote:
> Hi!
>
> I have a problem with both kvm pmemsave and memsave functions.
> (I know that both invoke the cpu_physical_memory_rw function)
>
> I'm trying to dump a guest physical memory region (sys_call_table for example).
> I know that , for example, the sys_call_table is stored at
> 0xffffffff8133c620 phys addr (found in System.map)
>
System.map lists virtual addresses, not physical addresses. Try memsave
instead.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-06-02 9:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 9:31 physical memory dump problem Matteo Signorini
2009-06-02 9:55 ` Avi Kivity [this message]
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=4A24F71C.7080005@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=signorinimatteo@gmail.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