Talk:Interrupt

From Wikipedia, the free encyclopedia

	This article is within the scope of Computing WikiProject, an attempt to build a comprehensive and detailed guide to computers and computing. If you would like to participate, you can edit the article attached to this page, or visit the project page, where you can join the project and/or contribute to the discussion.
Start	This article has been rated as start-Class on the quality scale
Low	This article has been rated as low-importance on the importance scale

Contents 1 Relating Interrupt Articles 1.1 Specific Harertertdware: 1.2 General Hardware: 1.3 General Information 1.4 Software 1.5 Interruption 2 Asynchrounous? 3 how come this article does not contain a paragraph about 'IRR'

[edit] Relating Interrupt Articles

There are a number of interrupt articles that seem to have no direction and a large amount of redundant information. I'm trying to organize them as I track them down.

I figure the layout should be as given below. There should be a seperate page for each Main. Each page short have redundent content eliminated, instead links should be placed to the appropriate main page. Of course, each Main page should be expanded apon. This includes a good introduction, history, features, programming information, references, etc.

Feel free to add additional links to this collection.

Catagory: Category: Interrupts

[edit] Specific Harertertdware:

• Main: Intel 8259
  • Redirects: Intel 8259A, 8259, 8259A, 8259B
• Main: Intel APIC Architecture
  • Redirects: Local APIC, IOAPIC, IO-APIC

• Main: STI (x86 instruction)
• Main: CLI (x86 instruction)
• Main: INT (x86 instruction)
  • Redirects: X86-int

[edit] General Hardware:

• Main: Programmable Interrupt Controller
  • Redirects: Interrupt controller
• Main: Advanced Programmable Interrupt Controller
  • Redirects: APIC, Apic
• Main: Maskable interrupt
  • Redirects: Masked interrupt
• Main: Non-Maskable interrupt
  • Redirects: Non-Maskable Interrupt, Non-maskable interrupt, Non maskable interrupt, Non-Maskable Interrupts, Non-Maskable interrupts,
• Main: Interprocessor Interrupt
  • Disambig: IPI

• TODO: Interrupt request register, Interrupt mask register, In-Service register
  • Disambig: IMR, ISR, IRR

[edit] General Information

• Main: Interrupt
  • Redirects: Interrupts, Hardware interrupt, Software Interrupt, Spurious Interrupt, Interrupt mask

• Main: Interrupt request
  • Redirects: Interrupt Request, IRQ
• Main: Polled Interrupts

• Main: End of Interrupt
  • Redirects: EOI

• Main: Interrupt Descriptor Table
  • Disambig: IDT
• Main: Interrupt vector
  • Disambig: IVT

• Main: SPL (computer science)
  • Disambig: SPL
• Main: Interrupt priority level
  • Disambig: IPL

[edit] Software

• Main: Interrupt handler
  • Redirects: Interrupt Handler, Interrupt routines, Interrupt Service Routine, Interrupt service routine

[edit] Interruption

• Main: Interrupt Storm
  • Redirects: Interrupt storm
• Main: Interrupt latency
  • Redirects: Interrupt Latency
• Main: Livelock (computer science)

This thingy is kinda weird. It freaks me out. Yeah, so... that's it.

[edit] Asynchrounous?

From article: "an interrupt is an asynchronous signal from hardware or software indicating the need for attention". The article later goes on to explain synchronous interrupts caused by software. I am not an expert on this but this appears to be an error. -- Bubbachuck 05:07, 28 October 2006 (UTC)

"Synchronous interrupts" aren't really interrupts. 195.224.75.71 13:48, 21 November 2006 (UTC)

Ashu on wiki 01:20, 12 December 2006 (UTC) An interrupt is understood by the processor only when it is checked for. So, if a processor checks for interrupts only after the execute cycle of an instruction, even an asynchronous interrupt cannot be understood at any other time. Software interrupts are more predicatble in the sense that they can be part of dry run of a program. On the other hand, interrupts caused by other hardware is completely unpredictable for the program.

[edit] how come this article does not contain a paragraph about 'IRR'

IRR redirects here. but i can't find no explanation. --