kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Sahibzada Irfanullah <irfan.gomalian@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Generating Log of Guest Physical Addresses from a Kernel Function and Perform Analysis at Runtime
Date: Tue, 24 Sep 2019 07:16:38 -0400	[thread overview]
Message-ID: <242780.1569323798@turing-police> (raw)
In-Reply-To: <CAGaWEboQtbz=z6wW28fE+r1qvdoZASvStVF4GAryz9R+crL1-w@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 850 bytes --]

On Tue, 24 Sep 2019 19:10:59 +0900, Sahibzada Irfanullah said:

> My actual goal is to generate log of physical addresses for different
> applications by writing them into the file, and then perform some analysis

What makes you think that the log of physical addresses will tell you anything
useful or interesting?

Hint:  Pretty much all physical pages usable for process space are identical as far
as the kernel is concerned, and if a virtual or disk cache page is pulled into memory
from disk more than once, the same virtual page can end up in different physical
pages.each time.

> at runtime in this function by reading the logs from the log file.
> Furthermore, I want a file which size can dynamically grow as the size of
> log increases.

Are you trying to do this *at runtime in real time*, or is post-run analysis OK?


[-- 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

  reply	other threads:[~2019-09-24 11:17 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 [this message]
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
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=242780.1569323798@turing-police \
    --to=valdis.kletnieks@vt.edu \
    --cc=irfan.gomalian@gmail.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).