From: Brian Gerst <bgerst@didntduck.org>
To: Robert Love <rml@tech9.net>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Clean up x86 interrupt entry code
Date: Sat, 06 Apr 2002 15:15:49 -0500 [thread overview]
Message-ID: <3CAF5775.2020401@didntduck.org> (raw)
In-Reply-To: <3CAF54AA.1020303@didntduck.org> <1018123940.899.104.camel@phantasy>
Robert Love wrote:
> On Sat, 2002-04-06 at 15:03, Brian Gerst wrote:
>
>
>>-ENTRY(ret_from_intr)
>>- GET_THREAD_INFO(%ebx)
>>- init_ret_intr
>>+ret_from_intr:
>>+ preempt_stop
>>+ DEC_PRE_COUNT(%ebx)
>
>
> You removed GET_THREAD_INFO and there does not seem to be a
> replacement. Is there some assurance *thread_info is now pointed to by
> %ebx here?
>
> Robert Love
>
Yes. It is set before the INC_PRE_COUNT and since it is preserved by
called functions it is still set when it gets to ret_from_intr.
--
Brian Gerst
next prev parent reply other threads:[~2002-04-06 20:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 20:03 [PATCH] Clean up x86 interrupt entry code Brian Gerst
2002-04-06 20:11 ` Robert Love
2002-04-06 20:15 ` Brian Gerst [this message]
2002-04-06 20:18 ` Linus Torvalds
2002-04-06 21:45 ` Robert Love
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=3CAF5775.2020401@didntduck.org \
--to=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
--cc=torvalds@transmeta.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