Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757286Ab0HaMhx (ORCPT ); Tue, 31 Aug 2010 08:37:53 -0400 Received: from fanny.its.uu.se ([130.238.4.241]:56403 "EHLO fanny.its.uu.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755941Ab0HaMhw (ORCPT ); Tue, 31 Aug 2010 08:37:52 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <19580.63387.632626.657277@pilspetsen.it.uu.se> Date: Tue, 31 Aug 2010 14:37:47 +0200 From: Mikael Pettersson To: Alexander Shishkin Cc: lkml@vger.kernel.org, Russell King , linux-kernel@vger.kernel.org, David Howells , "H. Peter Anvin" , Andrew Morton , Christoph Hellwig , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH 2/7] wire up sys_time_change_notify() on ARM In-Reply-To: <1283255151-6364-2-git-send-email-virtuoso@slind.org> References: <1283255151-6364-1-git-send-email-virtuoso@slind.org> <1283255151-6364-2-git-send-email-virtuoso@slind.org> X-Mailer: VM 7.17 under Emacs 20.7.1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2124 Lines: 55 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 > CC: Russell King > CC: Andrew Morton > CC: David Howells > CC: Christoph Hellwig > CC: "H. Peter Anvin" > 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 /Mikael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/