From: David Miller <davem@davemloft.net>
To: hpa@zytor.com
Cc: dean@arctic.org, ejbosman@cs.vu.nl, mtk.manpages@gmail.com,
akpm@linux-foundation.org, tglx@linutronix.de, mingo@redhat.com,
andrea@cpushare.com, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, arjan@infradead.org
Subject: Re: [PATCH 2/3] x86: Implement prctl PR_GET_TSC and PR_SET_TSC
Date: Sat, 26 Apr 2008 17:47:35 -0700 (PDT) [thread overview]
Message-ID: <20080426.174735.117959877.davem@davemloft.net> (raw)
In-Reply-To: <4813CABD.7040603@zytor.com>
From: "H. Peter Anvin" <hpa@zytor.com>
Date: Sat, 26 Apr 2008 17:37:17 -0700
> dean gaudet wrote:
> >>>
> >> PR_SET/PR_GET are the common prefixes, though.
> >
> > that's not what's at issue... "PR_SET_TSC" reads "set the TSC" ... it
> > doesn't read "set the ability to use the rdtsc instruction".
> > PR_SET_RDTSC_ENABLE would seem to be more accurate... or even
> > PR_SET_CR4_TSD which is what it really does :)
> >
>
> The whole point I'm making is that any such name would inherently read
> x86-specific.
Agreed.
next prev parent reply other threads:[~2008-04-27 0:47 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
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 [this message]
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=20080426.174735.117959877.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=andrea@cpushare.com \
--cc=arjan@infradead.org \
--cc=dean@arctic.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
Powered by JetHome