* RFC: scheduler, and per-arch switch_to
@ 2002-02-11 13:29 Jeff Garzik
2002-02-11 14:06 ` Thomas Capricelli
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Jeff Garzik @ 2002-02-11 13:29 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Linux-Kernel list
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.
--
Jeff Garzik | "I went through my candy like hot oatmeal
Building 1024 | through an internally-buttered weasel."
MandrakeSoft | - goats.com
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: RFC: scheduler, and per-arch switch_to
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
2002-02-11 23:47 ` Ingo Molnar
2 siblings, 0 replies; 4+ messages in thread
From: Thomas Capricelli @ 2002-02-11 14:06 UTC (permalink / raw)
To: lkml
I agree. While porting to zeta (see previous mail), i've had a look at some
different arch/ implementation of switch_to(), and i have not been able to
understand why the third arg was given.
Anyway, I don't use it, and I'm happy with this new interface.
Thomas
On Monday 11 February 2002 14:29, 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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: RFC: scheduler, and per-arch switch_to
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
2002-02-11 23:47 ` Ingo Molnar
2 siblings, 0 replies; 4+ messages in thread
From: Russell King @ 2002-02-11 14:17 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Ingo Molnar, Linux-Kernel list
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: RFC: scheduler, and per-arch switch_to
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
@ 2002-02-11 23:47 ` Ingo Molnar
2 siblings, 0 replies; 4+ messages in thread
From: Ingo Molnar @ 2002-02-11 23:47 UTC (permalink / raw)
To: Jeff Garzik; +Cc: Linux-Kernel list
On Mon, 11 Feb 2002, Jeff Garzik wrote:
> Do we really care about the third arg to the switch_to() macro?
we dont need it anymore, i'll remove it in my next patchset (if you dont
beat me at it).
Ingo
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2002-02-11 21:49 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2002-02-11 23:47 ` Ingo Molnar
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox