linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christopher Covington <cov@codeaurora.org>
To: linux-perf-users@vger.kernel.org, criu@openvz.org
Subject: Periodic checkpointing (using perf and signals?)
Date: Wed, 17 Jul 2013 11:44:00 -0400	[thread overview]
Message-ID: <51E6BBC0.1080102@codeaurora.org> (raw)

Hi,

I'm interested in taking checkpoints of processes from fast systems like
hardware and restoring them on really slow software models for performance
analysis. So far I've been able to save and restore checkpoints on the
different systems using CRIU. Now I'm looking for some way to trigger the
checkpointing. One basic use case might be to take a process that runs for say
100M instructions and take a checkpoint every 10M instructions to be restored
as 10 parallel runs of the model.

I'm thinking of trying to use performance counters to trigger such behavior.
Does perf already have support for triggering things like this? If not, I'm
thinking of trying to work in the ability to send a signal, like stop, to the
process of interest once the specified count, such as 10M instructions, has
been reached. CRIU or a wrapper could then wait for process of interest to
stop, take the checkpoint, let the process continue, and then wait for it to
stop again or exit. Would such an approach make sense?

Thanks,
Christopher

-- 
Employee of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by the Linux Foundation.

             reply	other threads:[~2013-07-17 15:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-17 15:44 Christopher Covington [this message]
2013-07-17 15:57 ` [CRIU] Periodic checkpointing (using perf and signals?) Pavel Emelyanov

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=51E6BBC0.1080102@codeaurora.org \
    --to=cov@codeaurora.org \
    --cc=criu@openvz.org \
    --cc=linux-perf-users@vger.kernel.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).