All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric St-Laurent <ericstl34@sympatico.ca>
To: Lee Revell <rlrevell@joe-job.com>
Cc: tglx@linutronix.de, Maxim Levitsky <maximlevitsky@gmail.com>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Adrian Bunk <bunk@stusta.de>,
	Arjan van de Ven <arjan@infradead.org>,
	Len Brown <lenb@kernel.org>
Subject: Re: [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far
Date: Tue, 20 Mar 2007 01:36:35 -0400	[thread overview]
Message-ID: <1174368995.14239.3.camel@perkele> (raw)
In-Reply-To: <75b66ecd0703192204n503eb4d3g361064f66319dd4c@mail.gmail.com>

On Tue, 2007-20-03 at 01:04 -0400, Lee Revell wrote:

> I think CONFIG_TRY_TO_DISABLE_SMI would be excellent for debugging,
> not to mention people trying to spec out hardware for RT
> applications...

There is a SMI disabling module in RTAI, check the smi-module.c in this:

https://www.rtai.org/RTAI/rtai-3.5.tar.bz2

More infos:

http://www.captain.at/rtai-smi-high-latency.php
http://www.captain.at/xenomai-smi-high-latency.php

It might make sense to merge this code, at least in the -rt tree.


- Eric



  reply	other threads:[~2007-03-20  5:36 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 10:30 [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Maxim Levitsky
2007-03-16 23:19 ` Len Brown
2007-03-17 23:00   ` Maxim
2007-03-17 23:32     ` Thomas Gleixner
2007-12-30  7:50       ` Mike Galbraith
2007-12-30 14:53         ` Ingo Molnar
2007-03-20 11:54     ` sysfs ugly timer interface (was Re: [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far) Pavel Machek
2007-03-22 15:28       ` Greg KH
2007-03-22 15:41         ` Thomas Gleixner
2007-03-23  1:24         ` sysfs q [was: sysfs ugly timer interface] Jan Engelhardt
2007-03-23  4:48           ` Greg KH
2007-03-23  6:05             ` Jan Engelhardt
2007-03-16 23:39 ` [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Thomas Gleixner
2007-03-17 23:01   ` Maxim
2007-03-16 23:44 ` Thomas Gleixner
2007-03-17  0:04   ` [PATCH] i386: trust the PM-Timer calibration of the local APIC timer Thomas Gleixner
2007-03-17  7:22     ` Ingo Molnar
2007-03-17 13:24     ` Andi Kleen
2007-03-18  8:12     ` Andrew Morton
2007-03-18  8:45       ` Thomas Gleixner
2007-03-17  1:32   ` [BUG] 2.6.21-rc1,2,3 regressions on my system that I found so far Len Brown
2007-03-17  9:56     ` Thomas Gleixner
2007-03-17 11:05       ` Thomas Gleixner
2007-03-17 16:52       ` Thomas Gleixner
2007-03-17 10:32     ` Arjan van de Ven
2007-03-17 13:26       ` Andi Kleen
2007-03-20  4:27         ` Greg KH
2007-03-20  6:30           ` Thomas Gleixner
2007-03-20  9:14           ` Arjan van de Ven
2007-03-20 11:36           ` Andi Kleen
2007-03-20 11:41             ` Oliver Neukum
2007-03-17 22:45     ` Maxim
2007-03-20  5:04   ` Lee Revell
2007-03-20  5:36     ` Eric St-Laurent [this message]
2007-03-20  9:15       ` Arjan van de Ven
2007-03-20 18:04         ` Andy Lutomirski
2007-03-20 22:58         ` Eric St-Laurent

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=1174368995.14239.3.camel@perkele \
    --to=ericstl34@sympatico.ca \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=bunk@stusta.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maximlevitsky@gmail.com \
    --cc=mingo@elte.hu \
    --cc=rlrevell@joe-job.com \
    --cc=tglx@linutronix.de \
    /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.