[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.GSO.4.56.0804141349060.17644@keg.few.vu.nl>
Date: Mon, 14 Apr 2008 13:59:40 +0200 (CEST)
From: Erik Bosman <ejbosman@...vu.nl>
To: Michael Kerrisk <mtk.manpages@...il.com>
cc: Andrew Morton <akpm@...ux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>,
Andrea Arcangeli <andrea@...share.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
linux-kernel@...r.kernel.org,
Arjan van de Ven <arjan@...radead.org>
Subject: Re: [PATCH 2/3] x86: Implement prctl PR_GET_TSC and PR_SET_TSC
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.
This is what I would say. I hope it's clear.
Erik
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists