linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "K.R. Foley" <kr@cybsft.com>
Cc: Daniel Walker <dwalker@mvista.com>,
	Karsten Wiese <annabellesgarden@yahoo.de>,
	linux-kernel@vger.kernel.org
Subject: Re: Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24
Date: Tue, 12 Jul 2005 18:01:50 +0200	[thread overview]
Message-ID: <20050712160150.GA23943@elte.hu> (raw)
In-Reply-To: <42D3D7ED.7000805@cybsft.com>


* K.R. Foley <kr@cybsft.com> wrote:

> Ingo Molnar wrote:
> >* Daniel Walker <dwalker@mvista.com> wrote:
> >
> >
> >>I observed a situation on a dual xeon where IOAPIC_POSTFLUSH , if on, 
> >>would actually cause spurious interrupts. It was odd cause it's 
> >>suppose to stop them .. If there was a lot of interrupt traffic on one 
> >>IRQ , it would cause interrupt traffic on another IRQ. This would 
> >>result in "nobody cared" messages , and the storming IRQ line would 
> >>get shutdown.
> >>
> >>This would only happen in PREEMPT_RT .
> >
> >
> >does it happen with the latest kernel too? There were a couple of things 
> >broken in the IOAPIC code in various earlier versions.
> >
> >	Ingo
> 
> Is this why I have been able to boot the latest versions without the 
> noapic option (and without noticeable keyboard repeat problems) or has 
> it just been dumb luck?

yes, i think it's related - the IO-APIC code is now more robust than 
ever, and that's why any known-broken system would be important to 
re-check.

	Ingo

  reply	other threads:[~2005-07-12 16:04 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-12 10:23 Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24 Karsten Wiese
2005-07-12 14:02 ` Ingo Molnar
2005-07-12 14:25   ` Daniel Walker
2005-07-12 14:28     ` Ingo Molnar
2005-07-12 14:31       ` Daniel Walker
2005-07-12 14:46         ` Ingo Molnar
2005-07-12 14:56           ` Daniel Walker
2005-07-16  2:11             ` Daniel Walker
2005-07-16 17:11               ` Ingo Molnar
2005-07-12 14:47       ` K.R. Foley
2005-07-12 16:01         ` Ingo Molnar [this message]
2005-07-12 16:16           ` K.R. Foley
2005-07-13  0:02           ` William Weston
2005-07-13  0:04     ` Karsten Wiese
2005-07-13  0:08       ` William Weston
2005-07-15 12:05         ` Karsten Wiese
2005-07-16 19:32           ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2005-06-28 17:27 Karsten Wiese
2005-06-28 20:21 ` Ingo Molnar
2005-06-28 20:30   ` Ingo Molnar
2005-06-28 23:51     ` Karsten Wiese
2005-06-29  6:34       ` Ingo Molnar
2005-06-29  7:00         ` Ingo Molnar
2005-06-29  9:15           ` William Weston
2005-06-29 12:56             ` Ingo Molnar
2005-06-30  1:50               ` William Weston
2005-06-29 14:48             ` Karsten Wiese
2005-06-29 19:38               ` Ingo Molnar
2005-06-29 23:36                 ` Karsten Wiese
2005-06-30 17:52                   ` Karsten Wiese
2005-06-30 20:50                     ` Ingo Molnar
2005-06-30 22:27                       ` Karsten Wiese
2005-06-30 22:59                         ` William Weston
2005-07-01  1:00                           ` William Weston
2005-07-01  0:15                         ` Karsten Wiese
2005-07-01  7:18                         ` Ingo Molnar
2005-07-01 19:34                           ` Chuck Harding
2005-07-02  1:46                           ` William Weston
2005-07-02  2:02                             ` Lee Revell
2005-07-04  8:53                               ` William Weston
2005-07-04 11:16                                 ` Ingo Molnar
2005-07-13  1:18                                   ` Lee Revell
2005-07-13  1:28                                     ` Lee Revell
2005-07-13  6:35                                       ` Ingo Molnar
2005-07-13 17:20                                         ` Lee Revell
2005-07-03 14:04                             ` Ingo Molnar
2005-07-03 18:12                               ` Ingo Molnar
2005-07-07  1:26                                 ` William Weston
2005-07-07 10:48                                   ` Ingo Molnar
2005-06-08 11:28 [patch] Real-Time Preemption, -RT-2.6.12-rc6-V0.7.48-00 Ingo Molnar
2005-06-25  9:12 ` Ingo Molnar
2005-06-25 13:19   ` Gene Heskett
2005-06-25 14:39     ` Gene Heskett
2005-06-27 19:01       ` Real-Time Preemption, -RT-2.6.12-final-V0.7.50-24 Chuck Harding
2005-06-27 19:42         ` Chuck Harding
2005-06-27 21:08           ` Gene Heskett
2005-06-27 20:09         ` Daniel Walker
2005-06-27 20:28           ` Chuck Harding
2005-06-28  0:50             ` Daniel Walker
2005-06-28  7:53           ` Steven Rostedt
2005-06-28  8:18             ` Ingo Molnar
2005-06-28  8:34               ` Steven Rostedt
2005-06-28  9:12               ` Ingo Molnar
2005-06-28 15:26                 ` Michal Schmidt
2005-06-28 15:31                   ` Ingo Molnar
2005-06-28 18:50                     ` Chuck Harding
2005-06-28 22:16                 ` Chuck Harding
2005-06-29  0:32                   ` Chuck Harding
2005-06-28 15:54             ` Daniel Walker

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=20050712160150.GA23943@elte.hu \
    --to=mingo@elte.hu \
    --cc=annabellesgarden@yahoo.de \
    --cc=dwalker@mvista.com \
    --cc=kr@cybsft.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).