what problem do you want to solve by doing this? you seem to have a solution in mind and want linux to behave like some other system where this solution is the right one. maybe you have to adapt your solution to how unix works and get it cleaner, more crash proof and more portable on the way.
what do you mean with 'I know that it is possible to run user process in kernel mode', which example do you have in mind? I don't want to have to guess your thoughts, just tell us. there is no simple supervisor bit that lets you just do more, at least not on i386, and not every syscall goes through int80.
user space processes don't work in kernel mode, the programming model is totally different. code using the in kernel programming model is called modules. what you can do from user space is mmap()ing your device's i/o area and get interrupts via the UIO interface (cf. http://lwn.net/Articles/232575/) which only requires a very minimal kernel module just for receiving and transmitting the interrupts.
what do you want to solve
what problem do you want to solve by doing this? you seem to have a solution in mind and want linux to behave like some other system where this solution is the right one. maybe you have to adapt your solution to how unix works and get it cleaner, more crash proof and more portable on the way.
what do you mean with 'I know that it is possible to run user process in kernel mode', which example do you have in mind? I don't want to have to guess your thoughts, just tell us. there is no simple supervisor bit that lets you just do more, at least not on i386, and not every syscall goes through int80.
user space processes don't work in kernel mode, the programming model is totally different. code using the in kernel programming model is called modules. what you can do from user space is mmap()ing your device's i/o area and get interrupts via the UIO interface (cf. http://lwn.net/Articles/232575/) which only requires a very minimal kernel module just for receiving and transmitting the interrupts.