From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263188AbUELX1J (ORCPT ); Wed, 12 May 2004 19:27:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263199AbUELX1J (ORCPT ); Wed, 12 May 2004 19:27:09 -0400 Received: from palrel11.hp.com ([156.153.255.246]:36280 "EHLO palrel11.hp.com") by vger.kernel.org with ESMTP id S263188AbUELX1G (ORCPT ); Wed, 12 May 2004 19:27:06 -0400 From: David Mosberger MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16546.45767.833654.478258@napali.hpl.hp.com> Date: Wed, 12 May 2004 16:27:03 -0700 To: Andrew Morton Cc: davidm@hpl.hp.com, rddunlap@osdl.org, ebiederm@xmission.com, drepper@redhat.com, fastboot@lists.osdl.org, linux-kernel@vger.kernel.org Subject: Re: [Fastboot] Re: [announce] kexec for linux 2.6.6 In-Reply-To: <20040512161603.44c50cec.akpm@osdl.org> References: <20040511212625.28ac33ef.rddunlap@osdl.org> <40A1AF53.3010407@redhat.com> <40A243C8.401@redhat.com> <40A2517C.4040903@redhat.com> <20040512143233.0ee0405a.rddunlap@osdl.org> <16546.41076.572371.307153@napali.hpl.hp.com> <20040512152815.76280eac.akpm@osdl.org> <16546.42537.765495.231960@napali.hpl.hp.com> <20040512161603.44c50cec.akpm@osdl.org> X-Mailer: VM 7.18 under Emacs 21.3.1 Reply-To: davidm@hpl.hp.com X-URL: http://www.hpl.hp.com/personal/David_Mosberger/ Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >>>>> On Wed, 12 May 2004 16:16:03 -0700, Andrew Morton said: Andrew> But it needs work for the kexec requirement. Sorry, I wasn't suggesting that kexec should be done that way _now_. I don't think it's nearly as simple as just adding an entry point in the DSO. For example, how would strace be affected by the new entry points? The syscall entry path probably would have to be almost duplicated to do a syscall-number-free entry. What about syscall restarting? Would VDSO entry points work with statically linked binaries? etc. Perhaps Uli has answers to all of these, but no matter how you do it, it'd be a pretty dramatic shift in how applications interact with the kernel. --david