Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
From: Garrit Franke <garritfranke@gmail.com>
To: "Irfan Ullah (울라 이르판)" <irfan@dke.khu.ac.kr>
Cc: Greg KH <greg@kroah.com>,
	Linux Kernel List <kernelnewbies@kernelnewbies.org>
Subject: Re: Current Instruction Pointer Along Memory Access for A specific Process
Date: Thu, 11 Jun 2020 14:53:34 +0200
Message-ID: <CAD16O840r2xa=s3wm98EfJfgZ-pEj0_2m+O3HkGcSJ7fuQ5+Kw@mail.gmail.com> (raw)
In-Reply-To: <CA+mB8Ow_whmEYTGoxtXrTioP8JJSmNjQt6RKrUECUViWrG6r0g@mail.gmail.com>

Hi Irfan,

I just wanted to let you know that your mail got stuck in my spam
folder, because it's not in plain text.
Greg, correct me if I'm wrong, but kernel mails should always be in plain text.

On Wed, Jun 10, 2020 at 9:38 PM, Irfan Ullah (울라 이르판)
<irfan@dke.khu.ac.kr> wrote:
>
> Thank you. I want to analyze the memory accesses of virtual machines on a host system and propose efficient prefetchers. Currently, I am trying to generate the memory accesses and page faults in the order in which they occur. As said, I can gather page faults directly from "page faults kvm_mmu_page_fault()" at run time, but I didn't find the location of memory accesses for virtual machines.
> I will check the "perf" that how it could be useful.
>
> On Mon, Jun 8, 2020 at 9:35 PM Greg KH <greg@kroah.com> wrote:
>>
>> On Mon, Jun 08, 2020 at 09:28:37PM +0900, Irfan Ullah (울라 이르판) wrote:
>> > 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.
>>
>> That's an "odd" requirement, what problem are you trying to solve?
>>
>> Anyway, have you tried the 'perf' tool?  I think it will provide you
>> with everything you need here, right?
>>
>> good luck!
>>
>> greg k-h
>
>
>
> --
> 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
>   sahibzada.iu@gmail.com
> Skype: sahibzada_irfanullah
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies

      reply index

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

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='CAD16O840r2xa=s3wm98EfJfgZ-pEj0_2m+O3HkGcSJ7fuQ5+Kw@mail.gmail.com' \
    --to=garritfranke@gmail.com \
    --cc=greg@kroah.com \
    --cc=irfan@dke.khu.ac.kr \
    --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

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 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/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git