From: Robert Love <rml@tech9.net>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Brian Gerst <bgerst@didntduck.org>,
Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Clean up x86 interrupt entry code
Date: 06 Apr 2002 16:45:20 -0500 [thread overview]
Message-ID: <1018129520.899.113.camel@phantasy> (raw)
In-Reply-To: <Pine.LNX.4.33.0204061216570.26740-100000@penguin.transmeta.com>
On Sat, 2002-04-06 at 15:18, Linus Torvalds wrote:
> It seems to be always loaded by the common interrupt code (and %ebx is a
> call-saved register, so calling the interrupt handlers and returning
> doesn't clobber it).
True enough. I guess I should of done this from the beginning ...
> But testing it may be a good idea ;^p
Of course I will, but it is hard (and subject to Heisenberg principals)
to test that we preempt whenever necessary. Only with the patch I sent
you earlier am I seeing no missed preemptions ... now to work on the
egregiously long-held locks.
Robert Love
prev parent reply other threads:[~2002-04-06 21:45 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
2002-04-06 20:18 ` Linus Torvalds
2002-04-06 21:45 ` Robert Love [this message]
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=1018129520.899.113.camel@phantasy \
--to=rml@tech9.net \
--cc=bgerst@didntduck.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.