From: martinwguy@gmail.com (Martin Guy)
To: linux-arm-kernel@lists.infradead.org
Subject: Context Switching is Broken
Date: Thu, 10 Jun 2010 21:36:39 +0100 [thread overview]
Message-ID: <AANLkTimeZ6xawjcYfVDohBFcMbbLlC3h2gDs91CyGcBX@mail.gmail.com> (raw)
In-Reply-To: <20100610142015.GC32362@n2100.arm.linux.org.uk>
On 6/10/10, Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> On Thu, Jun 10, 2010 at 03:16:49PM +0100, Will Deacon wrote:
> > > On Thu, Jun 10, 2010 at 04:11:35AM -0700, Herman Swartz wrote:
> > > > Context switching is broken. The man page for context is example code
> > > > that doesn't work, but should. Does a bug report need to be submitted?
> > >
> > > $ man context
> > > No manual entry for context
> > >
>
> > Quite. man makecontext has a fairly scary example, maybe that's it.
>
> In which case it's a question for libc people - the kernel has nothing
> to do with makecontext, getcontext, setcontext and swapcontext.
>
> I believe for glibc, these are simply unimplemented on ARM, and linking
> a program which uses makecontext with glibc would result in the linker
> issuing:
>
> warning: makecontext is not implemented and will always fail
Indeed on ARM:
martin:~$ make makecontext
cc makecontext.c -o makecontext
/tmp/ccnapqW4.o: In function `main':
makecontext.c:(.text+0x110): warning: warning: getcontext is not
implemented and will always fail
makecontext.c:(.text+0x164): warning: warning: makecontext is not
implemented and will always fail
/tmp/ccnapqW4.o: In function `func1':
makecontext.c:(.text+0x24): warning: warning: swapcontext is not
implemented and will always fail
$ ./makecontext
Function not inplemented.
$
so?
M
next prev parent reply other threads:[~2010-06-10 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-10 11:11 Context Switching is Broken Herman Swartz
2010-06-10 14:01 ` Russell King - ARM Linux
2010-06-10 14:16 ` Will Deacon
2010-06-10 14:20 ` Russell King - ARM Linux
2010-06-10 20:36 ` Martin Guy [this message]
2010-06-10 21:18 ` Herman Swartz
2010-06-10 21:29 ` Martin Guy
2010-06-10 22:59 ` Russell King - ARM Linux
2010-06-10 23:26 ` Herman Swartz
2010-06-10 23:36 ` Russell King - ARM Linux
2010-06-10 23:22 ` Herman Swartz
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=AANLkTimeZ6xawjcYfVDohBFcMbbLlC3h2gDs91CyGcBX@mail.gmail.com \
--to=martinwguy@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).