All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, shawn@churchofgit.com,
	akpm@linux-foundation.org, avagin@openvz.org,
	xemul@parallels.com
Subject: Re: [rfc 1/2] timerfd: Implement show_fdinfo method
Date: Mon, 31 Mar 2014 23:51:50 +0400	[thread overview]
Message-ID: <20140331195150.GO4872@moon> (raw)
In-Reply-To: <alpine.DEB.2.02.1403312134570.14882@ionos.tec.linutronix.de>

On Mon, Mar 31, 2014 at 09:43:13PM +0200, Thomas Gleixner wrote:
> > Index: linux-2.6.git/fs/timerfd.c
> > ===================================================================
> > --- linux-2.6.git.orig/fs/timerfd.c
> > +++ linux-2.6.git/fs/timerfd.c
> > @@ -284,11 +284,20 @@ static ssize_t timerfd_read(struct file
> >  	return res;
> >  }
> >  
> > +static int timerfd_show(struct seq_file *m, struct file *file)
> > +{
> > +	struct timerfd_ctx *ctx = file->private_data;
> > +
> > +	return seq_printf(m, "clockid: %d ticks: %llu\n",
> > +			  ctx->clockid, (unsigned long long)ctx->ticks);
> > +}
> 
> And what gives you the flags which were used in timerfd_settime()
> along with the remaining time to expiry and the interval?

Ouch, indeed, I need to export them as well. Thanks a lot!

  reply	other threads:[~2014-03-31 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-31 17:54 [rfc 0/2] timerfd -- implement missing parts to checkpoint and restore timerfd state Cyrill Gorcunov
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 [this message]
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=20140331195150.GO4872@moon \
    --to=gorcunov@gmail.com \
    --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.