mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Shishkin <virtuoso@slind.org>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: lkml@vger.kernel.org, Russell King <linux@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org, David Howells <dhowells@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@lst.de>,
	linux-arm-kernel@lists.infradead.org,
	Alexander Shishkin <virtuoso@slind.org>
Subject: Re: [PATCH 2/7] wire up sys_time_change_notify() on ARM
Date: Tue, 31 Aug 2010 15:42:01 +0300	[thread overview]
Message-ID: <20100831124201.GI3003@shisha.kicks-ass.net> (raw)
In-Reply-To: <19580.63387.632626.657277@pilspetsen.it.uu.se>

On Tue, Aug 31, 2010 at 02:37:47 +0200, Mikael Pettersson wrote:
> Alexander Shishkin writes:
>  > sys_time_change_notify() is a new syscall with number and types of
>  > parameters such that no ARM-specific processing is needed.
>  > 
>  > Tested with 2.6.36-rc3 using Documentation/time-change-notify-example.c.
>  > 
>  > Signed-off-by: Alexander Shishkin <virtuoso@slind.org>
>  > CC: Russell King <linux@arm.linux.org.uk>
>  > CC: Andrew Morton <akpm@linux-foundation.org>
>  > CC: David Howells <dhowells@redhat.com>
>  > CC: Christoph Hellwig <hch@lst.de>
>  > CC: "H. Peter Anvin" <hpa@zytor.com>
>  > CC: linux-arm-kernel@lists.infradead.org
>  > CC: linux-kernel@vger.kernel.org
>  > ---
>  >  arch/arm/include/asm/unistd.h |    1 +
>  >  arch/arm/kernel/calls.S       |    1 +
>  >  2 files changed, 2 insertions(+), 0 deletions(-)
>  > 
>  > diff --git a/arch/arm/include/asm/unistd.h b/arch/arm/include/asm/unistd.h
>  > index d02cfb6..ce38a6f 100644
>  > --- a/arch/arm/include/asm/unistd.h
>  > +++ b/arch/arm/include/asm/unistd.h
>  > @@ -393,6 +393,7 @@
>  >  #define __NR_perf_event_open		(__NR_SYSCALL_BASE+364)
>  >  #define __NR_recvmmsg			(__NR_SYSCALL_BASE+365)
>  >  #define __NR_accept4			(__NR_SYSCALL_BASE+366)
>  > +#define __NR_time_change_notify		(__NR_SYSCALL_BASE+367)
>  >  
>  >  /*
>  >   * The following SWIs are ARM private.
>  > diff --git a/arch/arm/kernel/calls.S b/arch/arm/kernel/calls.S
>  > index afeb71f..f1e64ba 100644
>  > --- a/arch/arm/kernel/calls.S
>  > +++ b/arch/arm/kernel/calls.S
>  > @@ -376,6 +376,7 @@
>  >  		CALL(sys_perf_event_open)
>  >  /* 365 */	CALL(sys_recvmmsg)
>  >  		CALL(sys_accept4)
>  > +		CALL(sys_time_change_notify)
>  >  #ifndef syscalls_counted
>  >  .equ syscalls_padding, ((NR_syscalls + 3) & ~3) - NR_syscalls
>  >  #define syscalls_counted
> 
> No, you need to use 370 as the syscall number on ARM as 367-369
> have been assigned to the fanotify and prlimit64 syscalls; see
> 
> http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=6343/1

I'm aware of that, but I don't know how to synchronize this with Russell's
devel branch. This patchset applies against 2.6.36-rc3. I guess, when it
comes to merging it, I'll update it against Russell's tree.

Regards,
--
Alex

  reply	other threads:[~2010-08-31 12:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-31 11:45 [PATCH 1/7] [RFCv4] notify userspace about time changes Alexander Shishkin
2010-08-31 11:45 ` [PATCH 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin
2010-08-31 12:37   ` Mikael Pettersson
2010-08-31 12:42     ` Alexander Shishkin [this message]
2010-09-01  9:14   ` Russell King - ARM Linux
2010-09-01 11:02     ` Alexander Shishkin
2010-08-31 11:45 ` [PATCH 6/7] wire up sys_time_change_notify() on ia64 Alexander Shishkin
2010-08-31 11:45 ` [PATCH 7/7] wire up sys_time_change_notify() on s390 Alexander Shishkin
2010-08-31 11:53   ` Martin Schwidefsky
2010-08-31 12:49   ` Heiko Carstens
2010-08-31 12:53     ` Alexander Shishkin
2010-09-16 22:10 [PATCHv5 0/7] system time changes notification Alexander Shishkin
2010-09-16 22:10 ` [PATCH 2/7] wire up sys_time_change_notify() on ARM Alexander Shishkin

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=20100831124201.GI3003@shisha.kicks-ass.net \
    --to=virtuoso@slind.org \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=hch@lst.de \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=lkml@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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

all inboxes | Powered by JetHome®