All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard -rw- weinberger <richard.weinberger@gmail.com>
To: Andrew Lutomirski <luto@mit.edu>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [GIT pull] x86 vdso updates
Date: Fri, 27 May 2011 13:59:14 +0200	[thread overview]
Message-ID: <BANLkTi=UEJqGxAs5p2tA=KzddNOrXCfXfQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinOQ_C_-Bix4FTQxHqP3aavmTRrzg@mail.gmail.com>

On Fri, May 27, 2011 at 1:36 PM, Andrew Lutomirski <luto@mit.edu> wrote:
> On Fri, May 27, 2011 at 2:12 AM, Ingo Molnar <mingo@elte.hu> wrote:
>>
>> * Andy Lutomirski <luto@mit.edu> wrote:
>>
>>> On 05/26/2011 02:50 PM, Thomas Gleixner wrote:
>>> >       x86-64: Add time to vDSO
>>>
>>> And here's the glibc bug:
>>>
>>> http://sourceware.org/bugzilla/show_bug.cgi?id=12813
>>>
>>> Let the deprecation of the vsyscall page begin :)
>>
>> Yeah :-)
>>
>> On a related note, now that these bits are upstream, what are your
>> rough plans for doing the int81 vsyscall emulation patch?
>>
>> The int81 patch would actually be (much!) more important to the
>> average Linux user than getting rid of the vsyscall from static
>> binaries: the vsyscall is the last predictable executable address in
>> PIE daemons with a dangerous SYSENTER instruction in it ...
>>
>> I'd actually consider accelerating it into v2.6.40.
>
> Working on it slowly.  In principle I'm writing my thesis right now on
> things that have very little to do with software :)
>
> My rough plans for the near-term stuff are:
>
> 1. Move vvars out of the vsyscall page.  Otherwise we have at least
> one predictable syscall instruction every 1<<16 seconds because the
> time is executable.  It's prettier that way, too.
>
> 2. Remove the vsyscall64 sysctl.  That will reduce the number of
> vsyscalls that require the kernel's help to one.  (This is a bit
> unfortunate for UML users, but I'm not sure what to do about that.
> UML vgetcpu is already terminally broken.)

Can you please be a bit more precise on that?
When there is anything I can do, let me know...

-- 
Thanks,
//richard

  reply	other threads:[~2011-05-27 11:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 18:50 [GIT pull] x86 vdso updates Thomas Gleixner
2011-05-26 21:26 ` Andy Lutomirski
2011-05-27  6:12   ` Ingo Molnar
2011-05-27 11:36     ` Andrew Lutomirski
2011-05-27 11:59       ` richard -rw- weinberger [this message]
2011-05-27 12:10         ` Andrew Lutomirski
2011-05-27 14:59           ` richard -rw- weinberger
2011-05-27 15:05             ` Andrew Lutomirski
2011-05-29  9:51               ` richard -rw- weinberger
2011-05-29 14:57                 ` Andrew Lutomirski
2011-05-29 15:10                   ` richard -rw- weinberger
2011-05-29 15:28                     ` Andrew Lutomirski
2011-05-29 16:40                       ` richard -rw- weinberger
2011-05-27 14:54       ` Andrew Lutomirski
2011-05-28 15:35         ` Ingo Molnar
2011-05-29  1:41           ` Andrew Lutomirski
2011-05-29 14:39           ` Mikael Pettersson
2011-05-29 14:59             ` Andrew Lutomirski
2011-05-29 16:01               ` Mikael Pettersson
2011-05-29 16:35                 ` Andrew Lutomirski
2011-05-29 18:06                   ` Mikael Pettersson
2011-05-29 18:44                     ` Andrew Lutomirski
2011-05-30  3:26                       ` Andrew Lutomirski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=UEJqGxAs5p2tA=KzddNOrXCfXfQ@mail.gmail.com' \
    --to=richard.weinberger@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.