mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Erik Bosman" <ejbosman@cs.vu.nl>
Cc: "Michael Kerrisk" <mtk.manpages@gmail.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrea Arcangeli" <andrea@cpushare.com>,
	"Linus Torvalds" <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: [PATCH 2/3] x86: Implement prctl PR_GET_TSC and PR_SET_TSC
Date: Mon, 14 Apr 2008 14:21:27 +0200	[thread overview]
Message-ID: <cfd18e0f0804140521x4a2b97d9h393463b821b380dc@mail.gmail.com> (raw)
In-Reply-To: <Pine.GSO.4.56.0804141349060.17644@keg.few.vu.nl>

On Mon, Apr 14, 2008 at 1:59 PM, Erik Bosman <ejbosman@cs.vu.nl> wrote:
>
>
>
> On Mon, 14 Apr 2008, Michael Kerrisk wrote:
>
> > Erik,
> >
> > Could you CC me please on kernel-userland API changes.
> >
> > Also it would be helpful if you could provide a short paragraph
> > (plaintext is fine) that describes the new commands and would be
> > suitable for inclusion in the prctl.2 (
> > http://www.kernel.org/doc/man-pages/online/pages/man2/prctl.2.html )
> > man page -- would that be possible?
> >
> > Cheers,
> >
> > Michael
> >
>
> .TP
> .B PR_SET_TSC
> (Since Linux 2.6.??, only on x86)
> Set the state of the flag determining whether the timestamp counter
> can be read by the process. Pass
> \fBPR_TSC_ENABLE\fP to \fIarg2\fP to allow it to be read, or
> \fBPR_TSC_SIGSEGV\fP to generate a \fBSIGSEGV\fP when the process tries
> to read the timestamp counter.
> .TP
> .B PR_GET_TSC
> (Since Linux 2.6.??, only on x86)
> Get the state of the flag determining whether the timestamp counter
> can be read from \fIarg2\fP.

Thanks Erik.  Looks good as a first cut -- I may come back to you with
questions.

It sounds like this might go into mainline in 2.6.26, is that right?

Cheers,

Michael

  reply	other threads:[~2008-04-14 12:21 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-11 16:55 Erik Bosman
2008-04-12 19:49 ` Arjan van de Ven
2008-04-12 20:48   ` H. Peter Anvin
2008-04-12 21:05     ` Erik Bosman
2008-04-12 21:12       ` Arjan van de Ven
2008-04-13 21:51     ` Erik Bosman
2008-04-13 22:02       ` H. Peter Anvin
2008-04-14  8:42         ` Ingo Molnar
2008-04-13 22:24 ` [PATCH 2/3-REVISED] " Erik Bosman
2008-04-14  3:58   ` Arjan van de Ven
2008-04-14  8:48     ` Ingo Molnar
2008-04-14 10:57 ` [PATCH 2/3] " Michael Kerrisk
2008-04-14 11:59   ` Erik Bosman
2008-04-14 12:21     ` Michael Kerrisk [this message]
2008-04-26 22:47     ` dean gaudet
2008-04-26 22:51       ` H. Peter Anvin
2008-04-26 23:14         ` dean gaudet
2008-04-26 23:46           ` H. Peter Anvin
2008-04-27  0:29             ` dean gaudet
2008-04-27  0:37               ` H. Peter Anvin
2008-04-27  0:47                 ` David Miller
2008-04-15  7:29 ` Andrew Morton
2008-04-15  7:46   ` Ingo Molnar

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=cfd18e0f0804140521x4a2b97d9h393463b821b380dc@mail.gmail.com \
    --to=mtk.manpages@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andrea@cpushare.com \
    --cc=arjan@infradead.org \
    --cc=ejbosman@cs.vu.nl \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mtk.manpages@gmail.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®