mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@free-electrons.com>
To: ranjith kumar <ranjithproxy@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to know list of files accessed
Date: Mon, 13 Feb 2012 13:32:56 +0100	[thread overview]
Message-ID: <4F3902F8.3090905@free-electrons.com> (raw)
In-Reply-To: <CAG9fbzb=B66ku7bPWjJOZ7_EcShYqORypP8-hsvD-g7z9t4oHA@mail.gmail.com>

Hi Ranjith,

On 02/13/2012 12:30 PM, ranjith kumar wrote:
> Hi,
> Suppose I downloaded linux kernel.
> When I run "make", many of the .c files will be compiled.
> I want to know which .c files are compiles and which .c files are not compiled.
> Is there any way to know in linux?
An easy way is to run your command with 'strace' to trap all the calls
to 'open':

strace make 2>&1 | grep open
>
> Access time of the files which are compiled is not getting modified
> when I run "make" . why?
That's correct. As long as you don't read these files, there's no reason
to update their latest access time. Comparing access time with modified
time is a useful way to know which files haven't been read after being
modified.

Cheers

Michael.
-- 
Michael Opdenacker, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
+33 484 253 396


  reply	other threads:[~2012-02-13 12:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-13 11:30 ranjith kumar
2012-02-13 12:32 ` Michael Opdenacker [this message]
2012-02-14  4:44   ` Valdis.Kletnieks
2012-02-14  8:26     ` Matthias Schniedermeyer

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=4F3902F8.3090905@free-electrons.com \
    --to=michael.opdenacker@free-electrons.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ranjithproxy@gmail.com \
    /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

Powered by JetHome