From: Takeharu KATO <takeharu1219@ybb.ne.jp>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: boot time scheduling hile atomic
Date: Tue, 14 Jun 2005 21:41:08 +0900 [thread overview]
Message-ID: <42AED064.2090305@ybb.ne.jp> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B8593BC@ismail.innsys.innovsys.com>
Hi
IMHO, it is more preferable to change kernel thread creation mechanism adapting to
other architecture(in stead of tweaking exception handling) to solve the issue at least.
Of course, cleaning up the exception codes to adapt to ppc64 is also preferable from
code maintenance view.
Anyway, please try to apply the patch as follow:
http://ozlabs.org/ppc32-patches/patch.pl?id=318
Rune Torgersen wrote:
> Any patch forthcomming soon?
>
>
>>-----Original Message-----
>>From: linuxppc-dev-bounces@ozlabs.org
>>[mailto:linuxppc-dev-bounces@ozlabs.org] On Behalf Of
>>Benjamin Herrenschmidt
>>Sent: Wednesday, March 16, 2005 16:29
>>To: Takeharu KATO
>>Cc: linuxppc-dev list
>>Subject: Re: boot time scheduling hile atomic
>>
>>On Wed, 2005-03-16 at 23:07 +0900, Takeharu KATO wrote:
>>
>>>Hi Benjamin:
>>>
>>>I can not figure out why my previous patch is more preferable than
>>>later one.
>>>Could you explain the reason of that please.
>>
>>There may be other kernel bits calling syscall, it sounds saner to
>>always make sure we don't reschedule when in atomic (though
>>it's dubious
>>that it's allowed to do syscalls in atomic regions, let's be safe
>>there).
>>
>>In fact, we are thinking about consolidating the syscall
>>return path and
>>the normal irq return path like we did on ppc64.
>>
>>Ben.
>>
>>
>>_______________________________________________
>>Linuxppc-dev mailing list
>>Linuxppc-dev@ozlabs.org
>>https://ozlabs.org/mailman/listinfo/linuxppc-dev
>>
>>
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
next prev parent reply other threads:[~2005-06-14 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 14:23 boot time scheduling hile atomic Rune Torgersen
2005-06-14 12:41 ` Takeharu KATO [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-03 12:44 GCC4 fun Joerg Dorchain
2005-03-03 13:46 ` evilninja
2005-03-03 14:18 ` boot time scheduling hile atomic (was: GCC4 fun.) Joerg Dorchain
2005-03-04 7:57 ` Joerg Dorchain
2005-03-04 15:06 ` boot time scheduling hile atomic _evil
2005-03-10 4:51 ` Takeharu KATO
2005-03-10 7:28 ` Joerg Dorchain
2005-03-10 16:19 ` Takeharu KATO
2005-03-11 6:19 ` Takeharu KATO
2005-03-16 0:18 ` Benjamin Herrenschmidt
2005-03-16 5:24 ` Takeharu KATO
2005-03-16 5:49 ` Takeharu KATO
2005-03-16 6:28 ` Benjamin Herrenschmidt
2005-03-16 14:07 ` Takeharu KATO
2005-03-16 22:28 ` Benjamin Herrenschmidt
2005-03-17 0:46 ` Takeharu KATO
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=42AED064.2090305@ybb.ne.jp \
--to=takeharu1219@ybb.ne.jp \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.com \
/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).