Re: IRQ vector assignment for system call exception

>> On Sat, 2005-12-10 at 18:50 +0530, Gaurav Dhiman wrote:
>> > 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
-- 
-
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/

---

• Follow-Ups:
  • Re: IRQ vector assignment for system call exception
    • From: Arjan van de Ven <[email protected]>

• References:
  • IRQ vector assignment for system call exception
    • From: "yen" <[email protected]>
  • Re: IRQ vector assignment for system call exception
    • From: Gaurav Dhiman <[email protected]>
  • Re: IRQ vector assignment for system call exception
    • From: Arjan van de Ven <[email protected]>
  • Re: IRQ vector assignment for system call exception
    • From: Ingo Molnar <[email protected]>

• Prev by Date: [PATCH 1/3] *at syscalls: Implementation
• Next by Date: Re: [PATCH] ia64: disable preemption in udelay()
• Previous by thread: Re: IRQ vector assignment for system call exception
• Next by thread: Re: IRQ vector assignment for system call exception
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]