From: David Mosberger <davidm@napali.hpl.hp.com>
To: Andrew Morton <akpm@osdl.org>
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
Date: Wed, 12 May 2004 16:27:03 -0700 [thread overview]
Message-ID: <16546.45767.833654.478258@napali.hpl.hp.com> (raw)
In-Reply-To: <20040512161603.44c50cec.akpm@osdl.org>
>>>>> On Wed, 12 May 2004 16:16:03 -0700, Andrew Morton <akpm@osdl.org> 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
next prev parent reply other threads:[~2004-05-12 23:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-12 4:26 Randy.Dunlap
2004-05-12 5:00 ` Ulrich Drepper
2004-05-12 6:18 ` [Fastboot] " Eric W. Biederman
2004-05-12 15:33 ` Ulrich Drepper
2004-05-12 15:54 ` Eric W. Biederman
2004-05-12 16:31 ` Ulrich Drepper
2004-05-12 16:57 ` Eric W. Biederman
2004-05-12 21:32 ` Randy.Dunlap
2004-05-12 22:08 ` David Mosberger
2004-05-12 22:28 ` Andrew Morton
2004-05-12 22:33 ` David Mosberger
2004-05-12 23:16 ` Andrew Morton
2004-05-12 23:27 ` David Mosberger [this message]
2004-05-13 4:30 ` Christoph Hellwig
2004-05-13 5:05 ` Willy Tarreau
2004-05-13 5:21 ` William Lee Irwin III
2004-05-13 5:48 ` Christoph Hellwig
2004-05-13 6:06 ` Eric W. Biederman
2004-05-13 6:20 ` Andrew Morton
2004-05-13 6:39 ` Eric W. Biederman
2004-05-13 7:33 ` Christoph Hellwig
2004-05-13 7:37 ` Andrew Morton
2004-05-13 7:49 ` Christoph Hellwig
2004-05-13 8:04 ` Andrew Morton
2004-05-13 13:52 ` Eric W. Biederman
2004-05-13 15:02 ` Randy.Dunlap
2004-05-14 5:21 ` Eric W. Biederman
2004-05-14 18:14 ` Adam Litke
2004-05-15 2:25 ` Eric W. Biederman
2004-05-17 0:49 ` H. Peter Anvin
2004-05-12 5:05 ` [Fastboot] " Eric W. Biederman
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=16546.45767.833654.478258@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=akpm@osdl.org \
--cc=davidm@hpl.hp.com \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
/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®