blocks|key|966501|text|您可以从不同的来源获得中断:计时器、硬盘、网络等。每一个中断都将由不同的中断处理程序处理。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|966502|因此，如果来自源的中断(S1)到达，而来自源的另一个中断(S2)正在处理，则没有问题。两个中断都由不同的中断处理程序处理。|966503|另一方面，如果来自源(S)的中断到达，而该源的处理程序正在处理另一个中断，则处理程序将无法处理第二个中断，因为它不是以重入方式设计的(也就是说，它不能被中断，处理新的中断，然后返回处理原始中断)。|offset|length|966504|您可以查看理解Linux内核，了解在Linux内核中中断工作的详细信息。|966505|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Reentrancy_(computing)|1|http://shop.oreilly.com/product/9780596005658.do^0|0|0|1N|2|0|0|5|9|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@$F|W|G|X|1|Y]]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$F|10|G|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

You can get interrupts from different sources: timer, hard disk, network, etc. Each one of those interrupts will be handled by a different interrupt handler.

Therefore, if an interrupt from source (S1) arrives while another interrupt from source (S2) is being processed, there is no problem. Both interrupts are being handled by different interrupt handlers.

On the other hand, if an interrupt from source (S) arrives while the handler for that source is processing another interrupt, the handler will not be able to process the second one since it is not designed in a <a href="http://en.wikipedia.org/wiki/Reentrancy_(computing)" rel="noreferrer">reentrant</a> way (i.e., it cannot be interrupted, process the new interrupt, and then go back to process the original interrupt).

You may have a look at <a href="http://shop.oreilly.com/product/9780596005658.do" rel="noreferrer">Understanding the Linux Kernel</a> for detailed information on the way interrupts work in the Linux kernel.

blocks|key|715061|text|来自同一源的中断必须与当前活动的中断在相同的数据结构上操作。来自不同来源的中断将在不同的数据结构上运行。因此，除非两个中断足够聪明地协调它们的活动，否则不能同时从同一个源中激活两个中断，而且当前的设计阻止了它们的活动，这样程序员就不必担心这种复杂性了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|715062|以现实世界中的一个(人为的)例子为例，想象一张桌子，人们去取某样东西的票，那里有不同的职员，根据姓氏的不同范围的字母表。两个姓以A结尾的人不能同时取票，否则负责他们的办事员可能会弄错。但是，姓以A结尾的人可以同时取到以Z结尾的人的票，因为他们各自的办事员使用的是不同的名字和成堆的票，所以其中一个不会对另一个产生负面影响。|715063|在本例中，客户姓的字母是源，客户是中断。办事员是中断处理程序，名称列表和票堆是核心数据结构。|715064|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Interrupts from the same source will have to operate on the same data structures as the currently active interrupt. Interrupts from different sources will be operating on different data structures. So you can't have two interrupts from the same source active at the same time unless they were smart enough to coordinate their activities, and the current design prevents them from being active so that the programmer doesn't have to worry about that complexity.

Taking a (contrived) example from the real world, imagine a table where people go to pick up tickets for something, where there are different clerks for different ranges of the alphabet based on last name. Two people whose last name ends in A can't both pick up tickets at the same time because otherwise the clerk responsible for them might get confused and make a mistake. However, someone whose last name ends in A can pick up tickets at the same time as someone whose last name ends in Z because their respective clerks are operating on different lists of names and piles of tickets, so one won't negatively affect the other.

In this example, the letter of the customer's last name is the source, and the customer is the interrupt. The clerk is the interrupt handler, and the list of names and pile of tickets are the kernel data structures.

blocks|key|1446175|text|其他的答案都很棒，但要记住的另一件事是水平触发的中断。如果中断控制器没有禁用它正在触发的中断，那么一个级别触发的中断会在ISR有机会告诉硬件停止中断之前立即重新触发自己。通常情况下，ISR不仅需要重置PIC，还需要告诉harward它正在与其通话以闭嘴。如果硬件继续中断，那么堆栈就会溢出，操作系统就会崩溃。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1446176|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The other answers are great, but one other thing to bear in mind is level triggered interrupts. If the interrupt controller did not disable the interrupt it was triggering then a level triggered interrupt would immediately retrigger itself before the ISR got chance to tell the hardware to stop interrupting. Typically an ISR does not only need to reset the PIC, it also needs to tell the harward it is talking to to shut up. If the hardware were to keep interrupting then the stack would overflow and the OS would be toast.

It is said that 

<blockquote>
 When an interrupt is sent by the PIC, the PIC will not send another
 interrupt from that same source until it gets acknowledged through an
 I/O port. This is because interrupt handlers usually manipulate
 critical data structures and would not withstand being interrupted by
 new invocations of themselves (i.e. they are not reentrant).
</blockquote>

I don't understand. Is there something different between interrupts of the same source and different source?

Something about interrupts of the same source

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

据说当PIC发送中断时，PIC将不会从同一源发送另一个中断，直到通过I/O端口确认中断为止。这是因为中断处理程序通常操作关键的数据结构，并且经不起新的自身调用的干扰(即它们不是重入的)。我不明白。同一来源和不同来源的中断之间有什么不同吗？

问关于同一来源的中断的一些内容
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问关于同一来源的中断的一些内容EN