Messages in this thread | | | From | (Eric W. Biederman) | Subject | Re: [patch 2/4] [RFC] syscalls, x86: Add __NR_kcmp syscall v4 | Date | Tue, 24 Jan 2012 00:49:27 -0800 |
| |
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> writes:
> On Tue, 24 Jan 2012 11:17:16 +0400 > Cyrill Gorcunov <gorcunov@gmail.com> wrote: > >> On Mon, Jan 23, 2012 at 11:04:19PM -0800, H. Peter Anvin wrote: >> > On 01/23/2012 10:47 PM, Cyrill Gorcunov wrote: >> > >> >> > >> Why under /arch ? >> > >> >> > > >> > > Hi Kame, >> > > >> > > because I've tested it under x86 only. Once someone >> > > confirm it's needed on some else arch and does work >> > > as expected -- it wont be a problem to make it system >> > > wide. Until then -- I think better to stick with >> > > at least tested case. >> > > ... >> > >> > That's not a reason to put it in arch/ ... that's possibly a reason to >> > not map the system call on other architectures yet. >> > >> >> Where it should live then? In kernel/ or mm/ ? >> > > kernel/checkpoint_restart ? > > gathering related changes to a directory may help developpers joins later.... > To me, this makes seeing git log easy ;)
kernel/
The dominant use may be checkpoint restart but the code is not at all checkpoint restart specific.
Eric
| |