From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Brock <brock@polynubstudios.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Generating Log of Guest Physical Addresses from a Kernel Function and Perform Analysis at Runtime
Date: Thu, 26 Sep 2019 18:56:57 -0400 [thread overview]
Message-ID: <11620.1569538617@turing-police> (raw)
In-Reply-To: <06c386b11a18e72cf817bbcb86e5a55205b6907a.camel@polynubstudios.com>
[-- Attachment #1.1: Type: text/plain, Size: 1277 bytes --]
On Thu, 26 Sep 2019 20:05:57 +1000, Brock said:
> On Thu, 2019-09-26 at 15:45 +0900, Sahibzada Irfanullah wrote:
> > Thank you very for your help. I have checked the ftrace, and perf. I
> > think it won't work for me.I am not analyzing/tracing the the kernel.
> > I want to develop my own dynamic tool like Pin Tool (or moudule
> > which can be loaded/unloaded at run time dynamically), so that I can
> > easily tune/modify for different purposes , and to get any type of
> > specific information from the kernel/KVM, espcecially in the context
> > of virtualization (guest and/or host memory management). That's why I
> > take a start from generating the log of guest physical addresses from
> > the kernel by saving it to the file; with the passage of time, I will
> > add the funcationalities to it.
> > Thank you.
> I'm not sure if it's hardware addresses but you can get kernel/user/kvm
> page fault information with:
I admit I'm still mystified by the requirement for the hardware address rather than
the virtual address, when doing any sort of analytics is going to require mapping
back to a process and virtual address - and possibly incorrectly (consider a page fault
from an instruction in a shared library that's mmap'ed into 250 running processes, like
glibc...)
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2019-09-26 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 10:10 Generating Log of Guest Physical Addresses from a Kernel Function and Perform Analysis at Runtime Sahibzada Irfanullah
2019-09-24 11:16 ` Valdis Klētnieks
2019-09-24 11:26 ` Sahibzada Irfanullah
2019-09-24 18:55 ` Valdis Klētnieks
2019-09-25 2:44 ` Sahibzada Irfanullah
2019-09-25 7:00 ` Sahibzada Irfanullah
2019-09-25 9:38 ` Greg KH
2019-09-25 14:21 ` Ruben Safir
2019-09-25 17:08 ` Greg KH
2019-09-25 18:04 ` Ruben Safir
2019-09-26 6:45 ` Sahibzada Irfanullah
2019-09-26 10:05 ` Brock
2019-09-26 22:56 ` Valdis Klētnieks [this message]
2019-09-25 16:42 ` Valdis Klētnieks
2019-09-24 13:29 ` Greg KH
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=11620.1569538617@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=brock@polynubstudios.com \
--cc=kernelnewbies@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 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).