blocks|key|1861765|text|简短的回答：，它们是不同的东西。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1861766|系统调用是运行在操作系统上的软件对操作系统提供的服务的调用。|unordered-list-item|1861767|中断通常是外部硬件组件，将需要在软件中处理的事件通知CPU/微处理器(通常是驱动程序)。|1861768|我说通常是外部的，因为一些中断可以由软件(软中断)引起。|1861769|所有的系统呼叫都被打断了吗？取决于|1861770|所有的系统呼叫都中断了吗？不是|1861771|长答案：操作系统管理CPU时间和连接到CPU的其他硬件(内存、硬盘、键盘等等)。它公开允许用户程序访问底层硬件的服务，这些是系统调用。通常这些操作涉及分配内存、读取/写入文件、打印文档等。|1861772|当操作系统与其他硬件交互时，通常是通过驱动程序层进行交互，驱动层设置了硬件执行的任务，并在完成任务后中断，因此打印机可能会在打印文档或耗尽页面时中断。因此，通常情况下，系统调用会导致产生中断。|1861773|是否所有系统调用中断-取决于它们可能被实现为软中断。因此，当用户程序进行系统调用时，它会导致一个软中断，导致操作系统挂起调用进程，并处理请求本身，然后继续该进程。但是，我引用维基百科的话|1861774|对于许多RISC处理器来说，这(中断)是唯一提供的技术，但CISC体系结构(如x86+)支持附加技术。例如SYSCALL/SYSRET、SYSENTER/SYSEXIT+(这两种机制分别由AMD和Intel独立创建，但本质上是相同的)。这些是“快速”控制传输指令，旨在为系统调用的系统调用快速传输控制，而不需要中断的开销。|blockquote|1861775|entityMap^0|0|6|0|0|0|0|0|0|0|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$]]|$1|I|3|J|5|H|7|15|8|@]|D|@]|E|$]]|$1|K|3|L|5|6|7|16|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|19|8|@$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1C|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1D|8|@]|D|@]|E|$]]|$1|W|3|X|5|Y|7|1E|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|10|$]]

Short Answer: 
They are different things.

<ul>
<li>A system call is call by software running on the OS to services
provided by the OS.</li>
<li>An interrupt is usually external hardware component notifying the CPU/Microprocessor about an event that needs handling in software (usually a driver).</li>
</ul>

I say usually external, because some interrupts can be raised by software (soft interrupt)

Are all system calls interrupts? Depends

Are all interrupts system calls? No

Long answer:
The OS manages CPU time and other hardware connected to the CPU (Memory (RAM), HDD, keyboard, to name a few). It exposes services that allow user programs to access the underlying hardware and these are system calls. Usually these deal with allocating memory, reading/writing files, printing a document and so on.

When the OS interacts with other hardware it usually does so through a driver layer which sets-up the task for the hardware to perform and interrupt once the job is done, so the printer may interrupt once the document is printed or it runs out of pages. It is therefore often the case that a system call leads to generation of interrupts.

Are all system calls interrupts - Depends as they may be implemented as soft interrupts. So when a user program makes a system call, it causes a soft interrupt that results in the OS suspending the calling process, and handle the request itself, then resume the process. But, and I quote from Wikipedia,

<blockquote>
 "For many RISC processors this (interrupt) is the only technique provided, but
 CISC architectures such as x86 support additional techniques. One
 example is SYSCALL/SYSRET, SYSENTER/SYSEXIT (the two mechanisms were
 independently created by AMD and Intel, respectively, but in essence
 do the same thing). These are "fast" control transfer instructions
 that are designed to quickly transfer control to the OS for a system
 call without the overhead of an interrupt"
</blockquote>

blocks|key|1861821|text|问题的答案取决于底层硬件(有时还包括操作系统实现)。我一会儿再谈这件事。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1861822|在操作系统中，系统调用和中断有什么区别？|blockquote|1861823|中断处理程序和系统调用(和故障处理程序)的目的大致相同:将处理器切换到内核模式，同时提供对内核结构的不小心或恶意访问的保护。|1861824|中断由异步外部事件触发。系统调用(或故障或陷阱)是通过执行代码同步触发的。|1861825|所有的系统呼叫都被打断了吗？所有的系统呼叫都中断了吗？|1861826|系统调用不会中断，因为它们不是由硬件异步触发的。进程继续在系统调用中执行其代码流，但不在中断中执行。|1861827|话虽如此，英特尔的文档常常将中断、系统调用、陷阱和错误混为一谈，称为“中断”。|1861828|一些处理器对系统调用、陷阱、故障和中断的处理方式大致相同。其他(尤其是Intel)提供了不同的实现系统调用的方法。|1861829|在以相同方式处理上述所有内容的处理器中，每种类型的中断、陷阱和故障都有唯一的编号。处理器期望操作系统设置指向处理程序的指针的向量(数组)。此外，操作系统还可以使用一个或多个处理程序来实现系统调用。|1861830|根据可用处理程序的数量，操作系统可能对每个系统调用都有一个单独的处理程序，或者使用一个寄存器值来确定要执行的特定系统功能。|1861831|在这种系统中，可以以调用系统调用的方式同步执行中断处理程序。|1861832|例如，在VAX上，CHMK+#4指令调用第四个内核模式处理程序。在英特尔的土地上，有一个INT指令，大致相同。|offset|length|style|CODE|1861833|英特尔处理器支持SYSCALL机制，该机制提供了一种实现系统调用的不同方式。|1861834|entityMap^0|0|0|0|0|0|0|0|0|0|0|0|9|7|18|3|0|8|7|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@]|A|$]]|$1|E|3|F|5|6|7|18|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|19|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|1A|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1C|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|6|7|1G|8|@]|9|@]|A|$]]|$1|W|3|X|5|6|7|1H|8|@$Y|1I|Z|1J|10|11]|$Y|1K|Z|1L|10|11]]|9|@]|A|$]]|$1|12|3|13|5|6|7|1M|8|@$Y|1N|Z|1O|10|11]]|9|@]|A|$]]|$1|14|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|15|$]]

The answer to your question depends upon the underlying hardware (and sometimes operating system implementation). I will return to that in a bit.
<blockquote>
In an operating system, what is the difference between a system call and an interrupt?
</blockquote>
The purpose of an interrupt handler and a system call (and a fault handler) is largely the same: to switch the processor into kernel mode while providing protection from inadvertent or malicious access to kernel structures.
An interrupt is triggered by an asynchronous external event.
A system call (or fault or trap) is triggered synchronously by executing code.
<blockquote>
Are all system calls interrupts? Are all interrupts system calls?
</blockquote>
System calls are not interrupts because they are not triggered asynchronously by the hardware. A process continues to execute its code stream in a system call, but not in an interrupt.
That being said, Intel's documentation often conflates interrupt, system calls, traps, and faults, as &quot;interrupt.&quot;
Some processors treat system calls, traps, faults and interrupts largely the same way. Others (notably Intel) provide different methods for implementing system calls.
In processors that handle all of the above in the same way, each type of interrupt, trap, and fault has a unique number. The processor expects the operating system to set up a vector (array) of pointers to handlers. In addition, there are one or more handlers available for an operating system to implement system calls
Depending upon the number of available handlers, the OS may have a separate handler for each system call or use a register value to determine what specific system function to execute.
In such a system, one can execute an interrupt handler synchronously the same way one invokes a system call.
For example, on the VAX the <code>CHMK #4</code> instruction, invokes the 4th kernel mode handler. In intel land there is an <code>INT</code> instruction that does roughly the same.
Intel processors have supported the <code>SYSCALL</code> mechanism that provides a different way to implement system calls.

In an operating system, what is the difference between a system call and an interrupt? Are all system calls interrupts? Are all interrupts system calls?

In an operating system, what is the difference between a system call and an interrupt?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

在操作系统中，系统调用和中断有什么区别？所有的系统呼叫都被打断了吗？所有的系统呼叫都中断了吗？

问在操作系统中，系统调用和中断有什么区别？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在操作系统中，系统调用和中断有什么区别？EN