You are required to read and agree to the below before accessing a full-text version of an article in the IDE article repository.
The full-text document you are about to access is subject to national and international copyright laws. In most cases (but not necessarily all) the consequence is that personal use is allowed given that the copyright owner is duly acknowledged and respected. All other use (typically) require an explicit permission (often in writing) by the copyright owner.
For the reports in this repository we specifically note that
- the use of articles under IEEE copyright is governed by the IEEE copyright policy (available at http://www.ieee.org/web/publications/rights/copyrightpolicy.html)
- the use of articles under ACM copyright is governed by the ACM copyright policy (available at http://www.acm.org/pubs/copyright_policy/)
- technical reports and other articles issued by M‰lardalen University is free for personal use. For other use, the explicit consent of the authors is required
- in other cases, please contact the copyright owner for detailed information
By accepting I agree to acknowledge and respect the rights of the copyright owner of the document I am about to access.
If you are in doubt, feel free to contact webmaster@ide.mdh.se
Analysis of software- and hardwareinterrupt handling(with and without cache)
Publication Type:
Conference/Workshop Paper
Venue:
Proceedings of the 3rd Design, Automation and Test Event
Abstract
In this article, we present a comparative study of hardware and software handling of external interrupts. The main parameter of the study is the response time from the hardware interrupt point to the start of interrupt handler task. The test platform used is a stand-alone card (PowerPC - processor, MPC860) with a bus logger (100ns-time tick). The software interrupt system used is a commercial standard real-time kernel, VRTX [VRTX] and the hardware system is RTU (Real-Time Unit) [RTU] with interrupt and scheduling in specialized hardware devices. The total response time in a software solution is the interrupt plus the scheduling latency. In a hardware solution, this is concurrent with the CPU and is faster. The test results are presented for both cases, viz., with and without cache. The study shows that hardware interrupt handling is faster, more predictable, simpler, and safer than the software handler.
Bibtex
@inproceedings{Lindh108,
author = {Lennart Lindh},
title = {Analysis of software- and hardwareinterrupt handling(with and without cache)},
month = {March},
year = {2000},
booktitle = {Proceedings of the 3rd Design, Automation and Test Event},
url = {http://www.es.mdu.se/publications/108-}
}