All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Suresh Siddha <suresh.b.siddha@intel.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Yinghai Lu <yinghai@kernel.org>,
	"Maciej W. Rozycki" <macro@linux-mips.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [patch] x86, apic: use 0x20 for the IRQ_MOVE_CLEANUP_VECTOR instead of 0x1f
Date: Wed, 13 Jan 2010 12:58:55 -0800	[thread overview]
Message-ID: <4B4E340F.7080106@zytor.com> (raw)
In-Reply-To: <m1vdf57nel.fsf@fess.ebiederm.org>

On 01/13/2010 12:36 PM, Eric W. Biederman wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
> 
>> On 01/11/2010 05:52 PM, Eric W. Biederman wrote:
>>>
>>> After having the documentation quoted at me.  I am having a distinct
>>> memory of one piece of documentation saying:
>>> "interrupts within a priority level can be delivered in any order"
>>>
>>> So I am guessing there is not any ordering of interrupts in the same
>>> priority level until they get to the local apic.
>>>
>>
>> There is no ordering of interrupts before they hit the local APIC, since
>> the local APIC is what would serialize them...
> 
> The io apic serializes them, and sends them over either the 2-wire
> bus or the front side bus.   How much serialization and prioritization
> happens at that point I am not certain, but some certainly happens
> before you get to the local apic.
> 

Specifically, from the 82093AA spec:

"The interrupt number or the vector does not imply a particular priority
for being sent.  The IOAPIC continually polls the 24 interrupts in a
rotating fashion, one at a time.  The pending interrupt polled first is
the one sent."

In other words, the prioritization is all done at the LAPIC.

	-hpa


  parent reply	other threads:[~2010-01-13 21:00 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-09  2:09 [patch] x86, apic: use 0x20 for the IRQ_MOVE_CLEANUP_VECTOR instead of 0x1f Suresh Siddha
2010-01-09  2:19 ` H. Peter Anvin
2010-01-09  2:50   ` Yinghai Lu
2010-01-11 22:53   ` Suresh Siddha
2010-01-11 22:57     ` H. Peter Anvin
2010-01-11 23:10       ` Eric W. Biederman
2010-01-11 23:13         ` H. Peter Anvin
2010-01-12  0:06           ` Suresh Siddha
2010-01-12  0:13             ` H. Peter Anvin
2010-01-12  0:28               ` Eric W. Biederman
2010-01-12  0:36                 ` H. Peter Anvin
2010-01-12  1:52                   ` Eric W. Biederman
2010-01-12  2:17                     ` H. Peter Anvin
2010-01-12  2:27                       ` Eric W. Biederman
2010-01-12 10:25                       ` Alan Cox
2010-01-13 20:36                       ` Eric W. Biederman
2010-01-13 20:38                         ` H. Peter Anvin
2010-01-13 20:53                         ` H. Peter Anvin
2010-01-13 20:58                         ` H. Peter Anvin [this message]
2010-01-12  0:42                 ` H. Peter Anvin
2010-01-11 23:00     ` Eric W. Biederman
2010-01-11 23:07       ` H. Peter Anvin
2010-01-09  3:07 ` Yinghai Lu
2010-01-09  3:20   ` H. Peter Anvin
2010-01-09  3:23 ` H. Peter Anvin

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=4B4E340F.7080106@zytor.com \
    --to=hpa@zytor.com \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --cc=yinghai@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 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.