From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: phillips@bonn-fries.net (Daniel Phillips)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
ian@ianduggan.net (Ian Duggan), rml@tech9.net (Robert Love),
linux-kernel@vger.kernel.org (linux kernel)
Subject: Re: 2.4.18 Preempt Freezeups
Date: Sun, 17 Mar 2002 03:31:24 +0000 (GMT) [thread overview]
Message-ID: <E16mROG-00083A-00@the-village.bc.nu> (raw)
In-Reply-To: <E16mNxQ-0000mM-00@starship> from "Daniel Phillips" at Mar 17, 2002 12:51:27 AM
> > Reviewing driver code for situations where it requires a small timing delay
> > and a large one is unacceptable
>
> Has anyone found one of those yet?
There are some frame buffers with that requirement. The stuff I've looked
at where the are such timing rules already disables interrupts.
(The other classic btw is older PIO IDE setups)
> > Checking anywhere you use the cpu id that you don't do somthing where it
> > might change under you (eg per cpu variables)
>
> Is per-cpu data the whole list there?
Think about profiling registers, mtrrs, msrs, and so forth. For example
if we had thread handling MCE traps we would hit a problem. As it happens
MCE is an interrupt so its all nice.
Alan
next prev parent reply other threads:[~2002-03-17 3:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-15 1:51 Ian Duggan
2002-03-15 1:54 ` Robert Love
2002-03-15 8:36 ` Ian Duggan
2002-03-15 14:30 ` Alan Cox
2002-03-15 21:36 ` Ian Duggan
2002-03-15 16:11 ` Mikael Pettersson
2002-03-15 14:25 ` Robert Love
2002-03-15 19:11 ` Robert Love
2002-03-16 0:40 ` yodaiken
2002-03-16 1:46 ` Mike Fedyk
2002-03-16 3:12 ` yodaiken
2002-03-17 0:33 ` Daniel Phillips
2002-03-17 1:13 ` yodaiken
2002-03-17 1:14 ` Daniel Phillips
2002-03-17 1:54 ` yodaiken
2002-03-17 2:08 ` Daniel Phillips
2002-03-17 21:17 ` Davide Libenzi
2002-03-15 2:11 ` Alan Cox
2002-03-15 8:38 ` Ian Duggan
2002-03-15 14:28 ` Alan Cox
2002-03-16 23:51 ` Daniel Phillips
2002-03-17 3:31 ` Alan Cox [this message]
2002-03-17 12:59 ` Dave Jones
2002-03-15 8:43 ` Daniel Phillips
2002-03-15 8:51 ` David S. Miller
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=E16mROG-00083A-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=ian@ianduggan.net \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=rml@tech9.net \
/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®