mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Masters <jcm@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH RT] add pending in fasteoi for IOAPIC hack
Date: Wed, 12 Dec 2007 22:35:40 -0500	[thread overview]
Message-ID: <1197516940.12653.5.camel@perihelion> (raw)
In-Reply-To: <Pine.LNX.4.58.0712121539400.22581@gandalf.stny.rr.com>

On Wed, 2007-12-12 at 15:41 -0500, Steven Rostedt wrote:
> The IOAPIC hack that does a level=>edge to mask does not disable
> interrupts. So we can receive interrupts when masked, and this means
> that we can miss interrupts that arrive when the thread is handling
> them.
> 
> This patch adds the "IRQ_PENDING" logic of the edge irqs to be
> able to catch interrupts coming in when supposably "masked".

ACK on all of these. I've been using them internally for a bit in
pursuit of a later problem. Additionally, I am currently reworking the
level->edge->level hack because it's known to be in violation of a
number of errata from third parties. The "legacy mode" hack is actually
only need on certain systems, which have e.g. a PCIe host bridge with
integrated IO-APIC that snoops the APIC to determine mask status.

I'm going to add a blacklist and quirks instead, as doing
level->edge->level otherwise causes us to start losing interrupts on
other systems. I will supply more information later - this is a somewhat
involved problem that we (Red Hat) have been looking at for a while.

Jon.



      reply	other threads:[~2007-12-13  3:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12 20:41 Steven Rostedt
2007-12-13  3:35 ` Jon Masters [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=1197516940.12653.5.camel@perihelion \
    --to=jcm@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    --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 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®