From: Arnd Bergmann <arnd@arndb.de>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Christopher Covington <cov@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Andrey Vagin <avagin@openvz.org>,
Pavel Emelyanov <xemul@parallels.com>,
Vladimir Davydov <vdavydov@parallels.com>,
Linux ARM kernel mailing list
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [patch 3/4] timerfd: Implement timerfd_ioctl method to restore timerfd_ctx::ticks
Date: Wed, 02 Jul 2014 21:01:02 +0200 [thread overview]
Message-ID: <4188254.Av1Z2pQssC@wuerfel> (raw)
In-Reply-To: <20140702170416.GG12440@moon>
On Wednesday 02 July 2014 21:04:16 Cyrill Gorcunov wrote:
> On Wed, Jul 02, 2014 at 12:49:51PM -0400, Christopher Covington 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))
> >
> > 64-bit get_user is currently unsupported on ARM, although it appears work is
> > ongoing [1].
> >
> > 1. https://lkml.org/lkml/2014/6/17/260
>
> Thanks for info, Christopher! What arm camp is using then, copy-from-user?
>
copy_from_user should work on all architectures. I believe a 64-bit get_user
is currently unsupported on most 32-bit architectures, x86-32 being a notable
exception.
Arnd
next prev parent reply other threads:[~2014-07-02 19:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 18:54 [patch 0/4] timerfd c/r support, v4 Cyrill Gorcunov
2014-06-23 18:54 ` [patch 1/4] timerfd: Implement show_fdinfo method Cyrill Gorcunov
[not found] ` <20140623190345.354980826-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-24 22:02 ` Cyrill Gorcunov
2014-06-23 18:54 ` [patch 2/4] docs: procfs -- Document timerfd output Cyrill Gorcunov
2014-06-23 18:54 ` [patch 3/4] timerfd: Implement timerfd_ioctl method to restore timerfd_ctx::ticks Cyrill Gorcunov
[not found] ` <20140623190345.499956567-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-24 22:03 ` Cyrill Gorcunov
2014-07-02 16:49 ` Christopher Covington
[not found] ` <53B4382F.9030908-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-07-02 17:04 ` Cyrill Gorcunov
2014-07-02 19:01 ` Arnd Bergmann [this message]
2014-07-02 19:07 ` Cyrill Gorcunov
2014-07-02 19:36 ` Cyrill Gorcunov
2014-06-23 18:54 ` [patch 4/4] timerfd.2: Add ioctl method description Cyrill Gorcunov
[not found] ` <20140623185431.396309193-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2014-06-23 19:44 ` [patch 0/4] timerfd c/r support, v4 Andrew Vagin
2014-06-30 19:43 ` Cyrill Gorcunov
2014-07-15 13:54 ` Cyrill Gorcunov
2014-07-15 16:11 ` Thomas Gleixner
2014-07-15 16:25 ` Cyrill Gorcunov
2014-07-15 21:08 ` Thomas Gleixner
2014-07-15 21:14 ` Cyrill Gorcunov
2014-07-15 21:16 ` Thomas Gleixner
2014-07-15 21:18 ` Cyrill Gorcunov
2014-07-15 21:20 ` Thomas Gleixner
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=4188254.Av1Z2pQssC@wuerfel \
--to=arnd@arndb.de \
--cc=akpm@linux-foundation.org \
--cc=avagin@openvz.org \
--cc=cov@codeaurora.org \
--cc=gorcunov@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=tglx@linutronix.de \
--cc=vdavydov@parallels.com \
--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 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).