Talk:Message Signaled Interrupts

This is the talk page for discussing improvements to the Message Signaled Interrupts article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Computing: Software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).
	This article is supported by Computer hardware task force (assessed as Mid-importance).

Unnamed section[edit]

The message is not written to 'system memory' but to a device that acts on the interrupt. That device might be in system memory space, i.e. memory mapped, but I doubt it can be read back and it definitely is not normal RAM.

Detail[edit]

This should have more detail. For example it should show the format of the information written and should explain how the appropriate interrupt handlers are identified and how the LAPIC/processor routes execution to the interrupt handlers. It should give an example of multiple interrupts for a single device. — Preceding unsigned comment added by 98.71.194.228 (talk) 14:28, 5 March 2015 (UTC)[reply]

Hello! Some might argue that adding such kind of information would turn an article into a manual, but I agree that adding such infomation would actually benefit this article. I might come back to your suggestion at some point in time. — Dsimic (talk | contribs) 23:08, 11 March 2015 (UTC)[reply]