On Wed, Jun 11, 2014 at 11:51:25AM +0400, Cyrill Gorcunov wrote:
> On Wed, Jun 11, 2014 at 11:27:43AM +0400, Andrew Vagin wrote:
...
> +#ifdef CONFIG_CHECKPOINT_RESTORE
> +static long timerfd_ioctl(struct file *file, unsigned int cmd, unsigned long
> arg)
> +{
> + struct timerfd_ctx *ctx = file->private_data;
> + int ret = 0;
> +
> + switch (cmd) {
> + case TFD_IOC_SET_TICKS: {
> + u64 ticks;
> +
> + if (get_user(ticks, (u64 __user *)arg))
> + return -EFAULT;
> + spin_lock_irq(&ctx->wqh.lock);
> + ctx->ticks = ticks;
> + if (ticks)
> + wake_up_locked(&ctx->wqh);
Setting ticks to zero is equivalent to timerfd_read(), isn't it?
So do we need to re-arme the timer, if it's periodic?
> + spin_unlock_irq(&ctx->wqh.lock);
> + break;
> + }
> + default:
> + ret = -ENOTTY;
> + break;
> + }
> +
> +V return ret;
> +}
> +#endif
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
