From: Lakshitha Harshan <harshan.dll@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Memory Mapping
Date: Fri, 6 May 2011 20:20:18 +0530 [thread overview]
Message-ID: <BANLkTimE7mw_+ckunvAwpJJvVNSOBT6UrQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 245 bytes --]
Hi all,
I want to get the access to task structs in domUs to get the memory
addresses of code segments in each process. So how do I read/map the data
correctly which I get through xc_map_foreign_range or xc_map_foreign_batch?
Thanks,
Harshan
[-- Attachment #1.2: Type: text/html, Size: 306 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2011-05-06 14:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 14:50 Lakshitha Harshan [this message]
2011-05-06 15:31 ` Memory Mapping Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2009-02-16 16:58 Memory mapping Frederic Beck
2009-02-18 14:35 ` Frederic Beck
2005-05-16 19:55 Xeno-unstable crashing at boot Ian Pratt
2005-05-17 11:52 ` Mike Wray
2005-05-17 13:26 ` Keir Fraser
2005-05-17 16:01 ` memory mapping Grzegorz Milos
2005-05-17 16:09 ` Grzegorz Milos
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=BANLkTimE7mw_+ckunvAwpJJvVNSOBT6UrQ@mail.gmail.com \
--to=harshan.dll@gmail.com \
--cc=xen-devel@lists.xensource.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;
as well as URLs for NNTP newsgroup(s).