From: "Martin Schwidefsky" <schwidefsky@de.ibm.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19-pre3 s390 ret_from_fork patch
Date: Mon, 18 Mar 2002 15:04:09 +0100 [thread overview]
Message-ID: <OF0B4E478D.55DD4333-ONC1256B80.00443165@de.ibm.com> (raw)
>The 2.4.19-pre3 works just dandy as it is without this patch,
>but it is needed for O(1) scheduler. I think Martin was going
>to forward this into 2.5.x tree, where O(1) is standard.
>
>The problem is that schedule_tail() is supposed to unlock
>runqueue, but if interrupts are enabled before that happens,
>a timer tick may squeeze in and deadlock. I observed such
>situation myself.
>
>So, I would like this to be in 2.4.19 for the sake of O(1) users.
>Any objections?
No, not really. My fix for 2.5.6 simply removes the stosm because
the sysc_return will disable the interrupts soon after anyway.
blue skies,
Martin
Linux/390 Design & Development, IBM Deutschland Entwicklung GmbH
Schönaicherstr. 220, D-71032 Böblingen, Telefon: 49 - (0)7031 - 16-2247
E-Mail: schwidefsky@de.ibm.com
next reply other threads:[~2002-03-18 14:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 14:04 Martin Schwidefsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-15 18:44 Pete Zaitcev
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=OF0B4E478D.55DD4333-ONC1256B80.00443165@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zaitcev@redhat.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
all inboxes | Powered by JetHome®