From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267973AbUIJW6I (ORCPT ); Fri, 10 Sep 2004 18:58:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267968AbUIJW6I (ORCPT ); Fri, 10 Sep 2004 18:58:08 -0400 Received: from the-village.bc.nu ([81.2.110.252]:28338 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id S267973AbUIJWuk (ORCPT ); Fri, 10 Sep 2004 18:50:40 -0400 Subject: Re: `new' syscalls for m68k From: Alan Cox To: Geert Uytterhoeven Cc: Linux/m68k , Debian GNU/Linux m68k , uClinux list , Linux Kernel Development In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1094852893.18235.5.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 (1.4.6-2) Date: Fri, 10 Sep 2004 22:48:16 +0100 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Gwe, 2004-09-10 at 21:57, Geert Uytterhoeven wrote: > - Are sys_sched_[gs]etaffinity() needed for non-SMP? Not really > - I disabled [sg]et_thread_area() since sys_[gs]et_thread_area() are > missing. Do we have to implement them, or should we use some other > method for Thread Local Storage? Up to your implementation > - What about sys_vserver()? Vserver project - probably dead for 2.6 since the SELinux and other security modules can implement this same things (and a 2.6 vserver one assumes would do likewise) > - What about sys_kexec_load()? Depends if you support kexec