Re: IRQ vector assignment for system call exception

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2005-12-15 at 23:50 +0100, Jan Engelhardt wrote:
> >> 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?

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.


-
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/

[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]
  Powered by Linux