IRQ vector assignment for system call exception
Hi:
I have a quwstion. Why the number 128 is reserver for system call exception in
interrupt vectors? Why not other numbers? Are there any historical reasons? thanks.
--
Open WebMail Project (http://openwebmail.org)
2005/12/8, yen <[email protected]>:
Quoted 5 lines
Hi:
I have a quwstion. Why the number 128 is reserver for system call exception in
interrupt vectors? Why not other numbers? Are there any historical reasons? thanks.
0x80 stands in the middle of [0..0xff].
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
Quoted 11 lines · Coywolf Qi Hunt
2005/12/8, yen <[email protected]>:
Quoted 5 lines
Hi:
I have a quwstion. Why the number 128 is reserver for system call exception in
interrupt vectors? Why not other numbers? Are there any historical reasons? thanks.
0x80stands in the middle of [0..0xff].
--
Coywolf Qi Hunt
http://sosdg.org/~coywolf/
If he's looking for 'secret codes' in the kernel, he might look at:
LINUX_REBOOT_MAGIC2
LINUX_REBOOT_MAGIC2B
LINUX_REBOOT_MAGIC2C
... in linux-uname -r/include/linux/reboot.h Hint: Cvt dec to hex.
Cheers,
Dick Johnson
Penguin : Linux version 2.6.13.4 on an i686 machine (5589.55 BogoMips). Warning : 98.36% of all statistics are fiction.
.
****************************************************************
The information transmitted in this message is confidential and may be privileged. Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited. If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to [email protected] - and destroy all copies of this information, including any attachments, without reading or disclosing them.
Thank you.
yes, definetely a historical reason. System libraries need to know this vector to invoke system call.
-Gaurav
Quoted 5 lines · yen
Hi:
I have a quwstion. Why the number 128 is reserver for system call exception in
interrupt vectors? Why not other numbers? Are there any historical reasons? thanks.
Quoted 9 lines
--
Open WebMail Project (http://openwebmail.org)-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
- Gaurav
my blog: http://lkdp.blogspot.com/
--
Quoted 2 lines · Gaurav Dhiman
yes, definetely a historical reason. System libraries need to know this vector to invoke system call.
nowadays it's also mostly unused; sysenter and friends are used instead and they don't use this entry point.
Quoted 6 lines · Arjan van de Ven
Quoted 2 lines · Gaurav Dhiman
yes, definetely a historical reason. System libraries need to know this vector to invoke system call.
nowadays it's also mostly unused; sysenter and friends are used instead and they don't use this entry point.
note that some system-calls are still invoked via int80 by glibc, such as fork() - even on sysenter/syscall capable CPUs.
Ingo
Quoted 9 lines
Quoted 6 lines · Gaurav Dhiman
Quoted 2 lines
yes, definetely a historical reason. System libraries need to know this vector to invoke system call.
nowadays it's also mostly unused; sysenter and friends are used instead and they don't use this entry point.
note that some system-calls are still invoked via int80 by glibc, such as
fork()- even on sysenter/syscall capable CPUs.
OT: Any idea when glibc moves to use sysenter on capable CPUs?
Jan Engelhardt
Quoted 11 lines · Jan Engelhardt
Quoted 9 lines
Quoted 6 lines · Gaurav Dhiman
Quoted 2 lines
yes, definetely a historical reason. System libraries need to know this vector to invoke system call.
nowadays it's also mostly unused; sysenter and friends are used instead and they don't use this entry point.
note that some system-calls are still invoked via int80 by glibc, such as
fork()- even on sysenter/syscall capable CPUs.OT: Any idea when glibc moves to use sysenter on capable CPUs?
it has been doing that for a LOOOONG time
exception are syscalls that sysenter can't do (iirc 6 argument ones, and I suspect fork() because it's just "special", but all normal ones are done via sysenter already from even before 2.6.0 got released.