From: Russell King <rmk@arm.linux.org.uk>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux-Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: RFC: scheduler, and per-arch switch_to
Date: Mon, 11 Feb 2002 14:17:05 +0000 [thread overview]
Message-ID: <20020211141705.C21300@flint.arm.linux.org.uk> (raw)
In-Reply-To: <3C67C740.43AAD437@mandrakesoft.com>
In-Reply-To: <3C67C740.43AAD437@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Mon, Feb 11, 2002 at 08:29:36AM -0500
On Mon, Feb 11, 2002 at 08:29:36AM -0500, Jeff Garzik wrote:
> Do we really care about the third arg to the switch_to() macro?
>
> IMHO it would be nice to define the architecture context switch
> interface like
>
> void switch_to(struct thread_info *from, struct thread_info *to);
>
> because we don't really seem to do much with the third arg, AFAICS.
It used to be a method to get the previously running task struct so some
cleanup could be done after the actual switch. Before you think about
"oh, that's prev anyway" think about what happens when "prev" is in some
random compiler defined CPU register, and your switch_to function saves
and restores all CPU registers.
In our current implementation, it looks like the third arg is no longer
necessary - Ingo?
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2002-02-11 14:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 13:29 RFC: scheduler, and per-arch switch_to Jeff Garzik
2002-02-11 14:06 ` Thomas Capricelli
2002-02-11 14:17 ` Russell King [this message]
2002-02-11 23:47 ` Ingo Molnar
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=20020211141705.C21300@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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