From: Dave Hansen <haveblue@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: [PATCH] 4KB stack + irq stack for x86
Date: Fri, 04 Oct 2002 13:12:58 -0700 [thread overview]
Message-ID: <3D9DF64A.4050405@us.ibm.com> (raw)
In-Reply-To: 3D9DF34D.2030405@us.ibm.com
Dave Hansen wrote:
> I fixed the problems that I was having. thread_info->preempt_count is
> now used to store softirq state, unlike in 2.5.20. Preempt count was
> not preserved once the switch to the interrupt stack occurred. This
> caused two nested softirqs and a deadlock. It is fixed now.
That'll teach me to get excited and send a patch. Sorry about the
"Only in"'s. I also think that there is still a small race window in
the code that I sent. I think that the old preempt_count need to be
placed into the new thread_info's preempt_count _before_ the stack
switch occurs.
--
Dave Hansen
haveblue@us.ibm.com
WARNING: multiple messages have this Message-ID (diff)
From: Dave Hansen <haveblue@us.ibm.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: Andrew Morton <akpm@digeo.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: [PATCH] 4KB stack + irq stack for x86
Date: Fri, 04 Oct 2002 13:12:58 -0700 [thread overview]
Message-ID: <3D9DF64A.4050405@us.ibm.com> (raw)
In-Reply-To: 3D9DF34D.2030405@us.ibm.com
Dave Hansen wrote:
> I fixed the problems that I was having. thread_info->preempt_count is
> now used to store softirq state, unlike in 2.5.20. Preempt count was
> not preserved once the switch to the interrupt stack occurred. This
> caused two nested softirqs and a deadlock. It is fixed now.
That'll teach me to get excited and send a patch. Sorry about the
"Only in"'s. I also think that there is still a small race window in
the code that I sent. I think that the old preempt_count need to be
placed into the new thread_info's preempt_count _before_ the stack
switch occurs.
--
Dave Hansen
haveblue@us.ibm.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-10-04 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 20:00 [PATCH] 4KB stack + irq stack for x86 Dave Hansen
2002-10-04 20:12 ` Dave Hansen [this message]
2002-10-04 20:12 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2002-09-11 23:00 Dave Hansen
2002-09-18 3:22 ` Rusty Russell
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=3D9DF64A.4050405@us.ibm.com \
--to=haveblue@us.ibm.com \
--cc=akpm@digeo.com \
--cc=bcrl@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.