In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-10-21 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Development >
Share
Shulou(Shulou.com)06/01 Report--
This article will explain in detail how to deal with terminal sharing in the Linux system. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.
In the Linux system, multiple devices can share an interrupt number, and interrupt handlers that share the same interrupt form a linked list, and even programs that do not produce interrupts will be executed.
Shared handlers are similar to non-shared handlers in registration and operation, but there are three main differences:
* the parameter flags of request_irq () must set the SA_SHIRQ flag.
* the dev_id parameter must be unique for each registered interrupt handler. A pointer to any device structure meets this requirement; the device structure is usually chosen because it is unique and may be used by interrupt handlers. You cannot pass a null value to a shared handler.
* the interrupt handler must be able to tell whether its device is actually causing an interrupt. This requires not only the support of the hardware, but also the relevant processing logic in the processor. If the hardware does not support this function, the interrupt handler will be at a loss as to whether it is the corresponding device or other devices that share the interrupt line.
All drivers that share the breaklines must meet the above requirements. As long as any device is not shared according to the rules, the break line cannot be shared. When you specify the SA_SHIRQ flag to call request_irq (), you can succeed only if the break line is not currently registered, or if all registered handlers on that line specify SA_SHIRQ. Note that 2.6 is different from previous kernels in that shared handlers can be mixed with SA_ INTERRUPT. After the kernel receives an interrupt, it invokes each handler registered on the interrupt line in turn. Therefore, a handler must know whether it is responsible for the interrupt. If the device associated with it does not cause an interrupt, the handler should exit immediately. This requires the hardware device to provide a status register (or similar mechanism) so that the interrupt handler can check. There is no doubt that most hardware provides this functionality.
This is the end of the article on "how to deal with terminal sharing in the Linux system". I hope the above content can be of some help to you, so that you can learn more knowledge. if you think the article is good, please share it for more people to see.
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
The market share of Chrome browser on the desktop has exceeded 70%, and users are complaining about
The world's first 2nm mobile chip: Samsung Exynos 2600 is ready for mass production.According to a r
A US federal judge has ruled that Google can keep its Chrome browser, but it will be prohibited from
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
About us Contact us Product review car news thenatureplanet
More Form oMedia: AutoTimes. Bestcoffee. SL News. Jarebook. Coffee Hunters. Sundaily. Modezone. NNB. Coffee. Game News. FrontStreet. GGAMEN
© 2024 shulou.com SLNews company. All rights reserved.