mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Filipe Brandenburger <filbranden@google.com>,
	Andy Lutomirski <luto@amacapital.net>
Cc: Richard Larocque <rlarocque@google.com>,
	Ingo Molnar <mingo@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Michael Davidson <md@google.com>,
	Greg Thelen <gthelen@google.com>, X86 ML <x86@kernel.org>,
	Linux API <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/vdso: Add prctl to set per-process VDSO load
Date: Wed, 17 Sep 2014 01:46:02 -0700	[thread overview]
Message-ID: <54194A4A.7030104@zytor.com> (raw)
In-Reply-To: <CADU+-uCguxhkw259MefABuzOxvyK_F6bhwza0YhveCCJxEV8wQ@mail.gmail.com>

On 09/16/2014 11:21 PM, Filipe Brandenburger wrote:
> Hi Andy,
> 
> On Tue, Sep 16, 2014 at 10:00 PM, Andy Lutomirski <luto@amacapital.net> wrote:
>> I think that the patch should instead tweak the vvar mapping to tell
>> the vdso not to use rdtsc.  It should be based on this:
> 
> I've been working on this approach which extends the vvar from 2 to 3
> pages. The third page would initially be mapped to a zero page but
> then through a prctl a task could replace it with a real page that
> could then be inherited through fork and exec.
> 
> That would make it possible to have per-task vvar contents.
> 
> We could use some of those values as flags to indicate whether vdso
> routines may use RDTSC or not.
> 
> In the future, we're planning to also use that to store clock offsets
> so that we can ensure CLOCK_MONOTONIC works after CRIU migration
> without having to turn off the VDSO or have to always fallback to full
> syscalls on every case.
> 
> Do you think that would be a reasonable way to accomplish that?
> 

Why would we need/want per process vvar contents?  It seems better to
have the code swapped out.

	-hpa



  reply	other threads:[~2014-09-17  8:46 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-17  0:05 Richard Larocque
2014-09-17  0:13 ` Andi Kleen
2014-09-17  0:21   ` Richard Larocque
2014-09-17  0:27 ` Andy Lutomirski
2014-09-17  1:18   ` Richard Larocque
2014-09-17  5:00     ` Andy Lutomirski
2014-09-17  5:34       ` Andy Lutomirski
2014-09-17  6:21       ` Filipe Brandenburger
2014-09-17  8:46         ` H. Peter Anvin [this message]
2014-09-17 13:48           ` Filipe Brandenburger
2014-09-17 14:28           ` Andy Lutomirski
2014-09-19 19:27             ` Andy Lutomirski
2014-09-19 21:26               ` Richard Larocque
2014-09-19 22:02               ` Filipe Brandenburger
2014-09-19 22:09                 ` Andy Lutomirski
2014-09-19 22:19                   ` Filipe Brandenburger
2014-09-19 22:31                     ` Andy Lutomirski
2014-09-20  3:10                       ` Filipe Brandenburger
2014-09-20  3:27                         ` Andy Lutomirski
2014-09-20  3:46                           ` Filipe Brandenburger
2014-09-20  5:30                             ` Andy Lutomirski
2014-09-17 11:36 ` Kevin Easton

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=54194A4A.7030104@zytor.com \
    --to=hpa@zytor.com \
    --cc=filbranden@google.com \
    --cc=gthelen@google.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=md@google.com \
    --cc=mingo@redhat.com \
    --cc=rlarocque@google.com \
    --cc=tglx@linutronix.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome