From: Alexander Sirotkin <demiurg@ti.com>
To: Philippe De Swert <philippedeswert@scarlet.be>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: o32_ret_from_sys_call
Date: Thu, 09 Dec 2004 14:41:35 +0200 [thread overview]
Message-ID: <41B847FF.5080309@ti.com> (raw)
In-Reply-To: <I8GFGZ$181DD12A3DE3065A4DBC5982EAE9EA84@scarlet.be>
[-- Attachment #1: Type: text/plain, Size: 1790 bytes --]
Hi.
I do work with montavista kernel, but regarding this particular change -
I can see it in all kernels
(montavista, kernel.org and linux-mips). In kernel.org this change
happened between 2.4.18 and
2.4.19, don't know when exatcly it was introduced into other kernels.
10x.
Philippe De Swert wrote:
>Hi Alexander,
>
>Do you happen to work with a clean kernel or a montavista one?
>Montavista made a lot of changes which do not necessarely reflect in the
>normal kernel code (especially on irq, pre-emptiveness and PCI)
>
>
>
>>I have noticed that somewhere around 2.4.17 sys_sysmips() function from
>>sysmips.c
>>was rewritten and call to o32_ret_from_sys_call disappear. This function
>>(o32_ret_from_sys_call)
>>was responsible for calling do_softirq() after each system call. I'm
>>curious, what is the
>>current mechanism in mips 2.4.x that ensures that do_softirq is called
>>after system call ?
>>
>>
>
>regards,
>
>Philippe
>
>| Philippe De Swert -GNU/linux - uClinux freak-
>|
>| Stag developer http://stag.mind.be/
>| Emdebian developer: http://www.emdebian.org
>|
>| Please do not send me documents in a closed format. (*.doc,*.xls,*.ppt)
>| Use the open alternatives. (*.pdf,*.ps,*.html,*.txt)
>| Why? http://pallieter.is-a-geek.org:7832/~johan/word/english/
>
>-------------------------------------------------------
>NOTE! My email address is changing to ... @scarlet.be
>Please make the necessary changes in your address book.
>
>
>
>
>
--
Alexander Sirotkin
SW Engineer
Texas Instruments
Broadband Communications Israel (BCIL)
Tel: +972-9-9706587
________________________________________________________________________
"Those who do not understand Unix are condemned to reinvent it, poorly."
-- Henry Spencer
[-- Attachment #2: Type: text/html, Size: 2502 bytes --]
next prev parent reply other threads:[~2004-12-09 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 12:17 Philippe De Swert
2004-12-09 12:41 ` Alexander Sirotkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 12:03 o32_ret_from_sys_call Alexander Sirotkin
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=41B847FF.5080309@ti.com \
--to=demiurg@ti.com \
--cc=linux-mips@linux-mips.org \
--cc=philippedeswert@scarlet.be \
/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