From: iomartin@iomartin.net (Martin Ichilevici de Oliveira)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Translating physical/linear address to virtual address
Date: Fri, 2 Oct 2015 22:04:52 -0600 [thread overview]
Message-ID: <20151003040452.GA2106@gamayun> (raw)
In-Reply-To: <CAK7N6vpy3g022b+Au_uQqAEF4aK3g24702VcFnvxXCeJVe8SLw@mail.gmail.com>
Hello Anish,
On Fri, Oct 02, 2015 at 08:37:25PM -0700, anish singh wrote:
> On Fri, Oct 2, 2015 at 12:58 PM, martin <iomartin@iomartin.net> wrote:
>
> > Hello,
> >
> > I'm working with a kernel module that, through hardware events, gets a
> > list of physical and linear memory addresses accessed by a program. I
> > would like to convert these to the virtual addresses, as seen from the
> > user space.
> >
>
> what are you trying to achieve?
I'm collecting some stats about these addresses, namely the amount of
accesses to each page that happen under specific conditions (and thus
why I use hardware events, instead of a simple memory trace).
My goal is to use this data to make informed decisions on pages
distribution in NUMA machines (with libnuma). The problem is that, as
far as I understood, physical and linear addresses won't necessarily be
the same between runs of the same program. Virtual addresses, on the
other hand, can be made to be consistent (by turning address space layout
randomization off).
Using virtual addresses also have the advantage that I can do all memory
management in userspace, with libnuma.
Thank you,
Martin
next prev parent reply other threads:[~2015-10-03 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 19:58 Translating physical/linear address to virtual address martin
[not found] ` <CAK7N6vpy3g022b+Au_uQqAEF4aK3g24702VcFnvxXCeJVe8SLw@mail.gmail.com>
2015-10-03 4:04 ` Martin Ichilevici de Oliveira [this message]
2015-10-03 4:29 ` Ruben Safir
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=20151003040452.GA2106@gamayun \
--to=iomartin@iomartin.net \
--cc=kernelnewbies@lists.kernelnewbies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.