Edge Rewrite
// HTMLRewriter · presentation

This page was redesigned at the edge.

Cloudflare fetched the original article and streamed it through HTMLRewriter to apply an entirely new visual system without rebuilding the source page.

// request.cf · coarse context

A page that knows where it met you.

Only coarse request metadata is shown. This demo does not display or persist visitor IP addresses.

Country
US
Cloudflare location
CMH
Connection
HTTP/2
Language
Not provided

Ray ID: a21c494c3a2d5e37

Jump to content

Talk:Message Signaled Interrupts

Page contents not supported in other languages.
Add topic
From Wikipedia, the free encyclopedia
Latest comment: 11 years ago by Dsimic in topic Detail

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