Return Styles: Pseud0ch, Terminal, Valhalla, NES, Geocities, Blue Moon. Entire thread

The many software interrupts of Linux

Name: Anonymous 2005-12-19 5:04

So I'm working on coverting a project over from a DOS/Windows environment to a Linux environment.  The issue is that there are some custom written interrupt handlers that are used in the project, INT 60h to be exact.  In the DOS/Windows environment, the advantage is that this is a free interrupt that can have the vector address changed without any concerns for f-ing the OS.  However, despite the open-source nature of Linux, I can't seem to find something as simple as a list of all the software interrupts and what they direct to for Linux.

To make a long story short, does anyone know the list of all software interrupts for Linux and what they do, or know of where on the web you find it?  Google is unfortunately not being my friend for this.

Name: Anonymous 2005-12-19 6:38

Oh, I see. Software interrupts were used in MS-DOS because it has no virtual memory spaces. They aren't used in Windows NT or Linux, as you have kernel calls for it.

When a process is loaded, it's given a virtual memory space where it sits alone with all its threads, shared memory segments, the OS, and the hardware devices mapped to RAM. The process can't access other processes' memory or screw them, and the system will allocate real memory for all the memory pages you "touch". Part of these memory pages might be actually swapped to disk (or they might be memory mapped files), but this is handled transparently.

To call kernel functions, the process just calls a function in a specific address which is the same for all processes. The compiler will know what to do; just use the functions described in man, like open or dup.

Newer Posts
Don't change these.
Name: Email:
Entire Thread Thread List