mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Erik Bosman <ejbosman@cs.vu.nl>
To: Andi Kleen <andi@firstfloor.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	Arjan van de Ven <arjan@infradead.org>,
	Andrea Arcangeli <andrea@cpushare.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] Add prctl commands PR_GET_TSC and PR_SET_TSC
Date: Sun, 13 Apr 2008 11:44:46 +0200 (CEST)	[thread overview]
Message-ID: <Pine.GSO.4.56.0804131126080.28138@keg.few.vu.nl> (raw)
In-Reply-To: <87r6daw2ay.fsf@basil.nowhere.org>



On Sun, 13 Apr 2008, Andi Kleen wrote:

> Erik Bosman <ebn310@few.vu.nl> writes:
>
> >     This patch adds prctl commands that make it possible
> >     to deny the execution of timestamp counters in userspace.
> >     If this is not implemented on a specific architecture,
> >     prctl will return -EINVAL.
>
> You forgot to state why you need that?
>
> -Andi
>

I'm using it for deterministic replay. With this trap it is
possible to emulate the instruction using ptrace and knowing
the outcome. Deterministic replay can be useful, amongst other
things, for debugging and security (instructing your debugger
to undo instructions for example, to see what happened before
a fault.)

Not having this trap means emulation should be used to catch
the instruction, leading to bad performance.

Without the timestamp counter, the only instruction leading
to non-determinism (that I'm aware of) is the CPUID instruction
that returns on which core it runs, but that doesn't seem to
be used that much.

Erik Bosman

  reply	other threads:[~2008-04-13  9:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 16:54 Erik Bosman
2008-04-13  9:07 ` Andi Kleen
2008-04-13  9:44   ` Erik Bosman [this message]
2008-04-13 16:47     ` Andi Kleen
2008-04-13 19:29       ` H. Peter Anvin
2008-04-13 20:50         ` Andi Kleen
2008-04-13 20:53           ` H. Peter Anvin

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=Pine.GSO.4.56.0804131126080.28138@keg.few.vu.nl \
    --to=ejbosman@cs.vu.nl \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=andrea@cpushare.com \
    --cc=arjan@infradead.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®