Kernel Newbies archive on
 help / color / Atom feed
From: "Irfan Ullah (울라 이르판)" <>
To: Linux Kernel List <>
Subject: Current Instruction Pointer Along Memory Access for A specific Process
Date: Mon, 8 Jun 2020 21:28:37 +0900
Message-ID: <> (raw)

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

Hi everyone,
I am trying to generate the log of instruction pointers (IPs) along with
corresponding memory accesses (including the page faults) in a sequence for
a specific application. I have generated the log of page faults along with
corresponding memory addresses by modifying the Linux Kernel code for a
specific application, but  I didn't find the location of the
current instruction pointers along with corresponding memory addresses;
being analyzing Linux kernel code for more than a week. I think what I need
is available in the code related to the CPU control unit because it handles
the fetch-execute cycle; I looked for it but couldn't find the code
responsible for the fetch-execute cycle in the kernel code.

Could anyone suggest to me where could I find the current value of  IP
along with the memory address in the Kernel code?

 There are some tools available to generate the log of instruction pointers
with memory accesses but I can't use them because I need a log of memory
accesses and page faults in exact sequence and order along with
corresponding IPs.

Thank you.

*Best Regards,*

*Mr. Irfan Ullah*
PhD Candidate
Data and Knowledge Engineering(DKE) Lab
Department of Computer Science and Engineering
Kyung Hee University, South Korea.
 +82-010-591-51651 <+82%2010-3877-8867>
*Skype*: sahibzada_irfanullah

[-- Attachment #1.2: Type: text/html, Size: 2980 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

Kernelnewbies mailing list

             reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 12:28 Irfan Ullah (울라 이르판) [this message]
2020-06-08 12:35 ` Greg KH
2020-06-10  7:37   ` Irfan Ullah (울라 이르판)
2020-06-11 12:53     ` Garrit Franke

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Kernel Newbies archive on

Archives are clonable:
	git clone --mirror kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ \
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone