From: Ulrich Drepper <drepper@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Roland McGrath <roland@redhat.com>,
Christoph Lameter <clameter@sgi.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/7] cpu-timers: high-resolution CPU clocks for POSIX clock_* syscalls
Date: Tue, 14 Dec 2004 14:26:01 -0800 [thread overview]
Message-ID: <41BF6879.3090900@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0412141410150.3279@ppc970.osdl.org>
[-- Attachment #1: Type: text/plain, Size: 581 bytes --]
Linus Torvalds wrote:
> I'd vote for
> not exposing them any more than necessary (ie the current incidental "ps"
> interface is quite enough), at least until somebody can come up with a
> very powerful example of why exposing them is a good idea.
Indeed. It's so much easier to grant additional rights at a later time
than to take something away for whatever reasons.
Globally accessible clocks would need to have the semantic carefully
defined, SELinux hooks would have to be added etc.
--
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2004-12-14 22:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-14 3:55 Roland McGrath
2004-12-14 18:36 ` Christoph Lameter
2004-12-14 21:38 ` Ulrich Drepper
2004-12-14 21:50 ` Roland McGrath
2004-12-14 21:58 ` Christoph Lameter
2004-12-14 22:18 ` Linus Torvalds
2004-12-14 22:26 ` Ulrich Drepper [this message]
2004-12-14 22:44 ` Linus Torvalds
2004-12-14 23:08 ` Roland McGrath
2004-12-14 22:14 ` Roland McGrath
2004-12-14 22:23 ` Christoph Lameter
2004-12-15 18:43 ` Christoph Lameter
[not found] <200412140355.iBE3t7KL008040@magilla.sf.frob.com.suse.lists.linux.kernel>
2004-12-14 19:07 ` Andi Kleen
2004-12-14 22:44 ` Ulrich Drepper
2004-12-15 4:51 ` Andi Kleen
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=41BF6879.3090900@redhat.com \
--to=drepper@redhat.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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®