From: Ingo Molnar <mingo@elte.hu>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ingo Molnar <mingo@redhat.com>, Pavel Machek <pavel@ucw.cz>,
kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>
Subject: Re: Cleanups for APIC
Date: Thu, 27 May 2004 16:14:04 +0200 [thread overview]
Message-ID: <20040527141404.GA23566@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.55.0405271542080.10917@jurand.ds.pg.gda.pl>
* Maciej W. Rozycki <macro@ds2.pg.gda.pl> wrote:
> The I/O APIC need not be hooked to PCI ;-) -- I'm not sure about the
> i82093AA, but that's definitely true for the i82489DX. The call to
> io_apic_sync() is needed for masking to make sure interrupts won't be
> dispatched after returning from the call -- this is not needed for
> unmasking as a delay here is harmless.
well, an APIC message could be on the way to the CPU even with this
synchronization. Does it matter whether it's a newly dispatched one due
to POST delays or an in-fly one due to APIC bus delays?
Ingo
next prev parent reply other threads:[~2004-05-27 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 12:49 Pavel Machek
2004-05-27 13:15 ` Ingo Molnar
2004-05-27 13:30 ` Maciej W. Rozycki
2004-05-27 13:34 ` Ingo Molnar
2004-05-27 14:03 ` Maciej W. Rozycki
2004-05-27 14:14 ` Ingo Molnar [this message]
2004-05-27 14:26 ` Maciej W. Rozycki
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=20040527141404.GA23566@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--cc=mingo@redhat.com \
--cc=pavel@ucw.cz \
/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®