user processes that are given direct access to I/O ports ??
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
user processes that are given direct access to I/O ports ??
Hi all,
normally all I/O goes through the kernel so that it can schedule the operations and prevent processes from stepping on each other. A few special user processes are allowed to slide around the kernel, usually by being given direct access to I/O ports. X servers are the most common example of this isn't it ?.
can any one give examples for any other processes that are allowed to slide around the kernel ?
any program that runs as root may use direct i/o access, although they may need suid bit set to 1 for other reasons. Generally most shouldnt need it, but some may, im sure a google search will return a list someone has put together. why do you need it?
any program that runs as root may use direct i/o access, although they may need suid bit set to 1 for other reasons. Generally most shouldnt need it, but some may, im sure a google search will return a list someone has put together. why do you need it?
I doubt there are very many and i dont think the fact they use direct i/o is significant in any case. the most important thing to remember is the i/o ports are protected by the kernel and one must query the kernel through system calls (also known as 'interrupts', which while similar to hardware interrupts are not the exact same)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.