All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@openvz.org>
To: linux-kernel@vger.kernel.org
Cc: shawn@churchofgit.com, tglx@linutronix.de,
	akpm@linux-foundation.org, avagin@openvz.org,
	xemul@parallels.com, gorcunov@openvz.org
Subject: [rfc 0/2] timerfd -- implement missing parts to checkpoint and restore timerfd state
Date: Mon, 31 Mar 2014 21:54:07 +0400	[thread overview]
Message-ID: <20140331175407.400476950@openvz.org> (raw)

Timerfd interface provides to user-space almost all data needed to checkpoint
and restore it, the only missing parts are @clockid (and while @ticks can be
read by simple read() call there is no way to write its value back). The series
exports them to userspace via /proc/pid/fdinfo/N interface and with write()
call one can setup @ticks back to a timer.

Please take a look. This is rfc to figure out if there a better way
to handle timerfds (maybe ioctls with complete timer context or somthing).
Also I'm not sure in one aspect -- if someone sets non-zero @ticks to
a timer, should I mark it as expired? Thomas, could you please give
me some advice on it?

	Cyrill

             reply	other threads:[~2014-03-31 18:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 17:54 Cyrill Gorcunov [this message]
2014-03-31 17:54 ` [rfc 1/2] timerfd: Implement show_fdinfo method Cyrill Gorcunov
2014-03-31 19:43   ` Thomas Gleixner
2014-03-31 19:51     ` Cyrill Gorcunov
2014-03-31 17:54 ` [rfc 2/2] docs: procfs -- Document timerfd output Cyrill Gorcunov
2014-03-31 18:31   ` Andrey Wagin
2014-03-31 18:43     ` Cyrill Gorcunov

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=20140331175407.400476950@openvz.org \
    --to=gorcunov@openvz.org \
    --cc=akpm@linux-foundation.org \
    --cc=avagin@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shawn@churchofgit.com \
    --cc=tglx@linutronix.de \
    --cc=xemul@parallels.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.