lkml.org 
[lkml]   [2011]   [Jun]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v5 9/9] x86-64: Add CONFIG_UNSAFE_VSYSCALLS to feature-removal-schedule

* Andrew Lutomirski <luto@mit.edu> wrote:

> > don't even bother making it a config option for now. If we can
> > replace the vsyscall page with a page fault or int3 or whatever,
> > and it's only used for the 'time()' system call, just do it.
>
> Really?
>
> I won't personally complain about the 200+ ns hit, but I'm sure
> someone will cc: me on a regression report if there's no option.

Well, for 0.2 usecs to show up one would have to do like a million of
them per second.

Why an application would want to query the *same value* from the
kernel a million times per second is beyond me. vgettimeofday()?
Sure. But vtime()?

Thanks,

Ingo


\
 
 \ /
  Last update: 2011-06-06 23:57    [W:0.116 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site