From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Context Switching is Broken
Date: Fri, 11 Jun 2010 00:36:17 +0100 [thread overview]
Message-ID: <20100610233617.GA9865@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <938111.34490.qm@web51801.mail.re2.yahoo.com>
On Thu, Jun 10, 2010 at 04:26:47PM -0700, Herman Swartz wrote:
> Yes, the kernel has the functions, because the kernel uses them in
> it's operation. The glibc needs to implement these calls to the
> kernel. Do I have that right?
No. The kernel's context switching is entirely different to the
"context switching" that you're talking about here.
As I've said twice - and I'm not going to repeat it a third time -
this has nothing to do with the kernel and everything to do with
glibc.
You can see this from the i386 version of setcontext(), which can
be found in the glibc source code:
sysdeps/unix/sysv/linux/i386/setcontext.S
The only call this code makes to the kernel is to set the processes
signal mask - which ARM has provided since day 1, and is used for
many things other than providing this support. So there's nothing
to add to the kernel.
What's missing is the glibc support code. Not the kernel code.
You need to talk to glibc people about this, not kernel people.
next prev parent reply other threads:[~2010-06-10 23: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
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 [this message]
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=20100610233617.GA9865@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).