From: Greg KH <greg@kroah.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org
Subject: Re: [PATCH 2/2] posix clocks: introduce a sysfs presence.
Date: Fri, 10 Sep 2010 17:20:20 -0700 [thread overview]
Message-ID: <20100911002020.GA20252@kroah.com> (raw)
In-Reply-To: <20100910093135.GB10179@riccoc20.at.omicron.at>
On Fri, Sep 10, 2010 at 11:31:35AM +0200, Richard Cochran wrote:
> On Fri, Sep 10, 2010 at 12:00:08AM +0100, Alan Cox wrote:
> > Also we have existing time sources that don't follow the poxix clock
> > model - I can open /dev/rtc and I can open the hpet and so on.
> >
> > I like /sys/class/time* *but* you need to be able to open the sysfs
> > device and apply operations to it in order for it to work when your closk
> > can be dynamically created and destroyed and to get a sane Unix API.
> >
> > To start with try applying permissions to clock sources via the POSIX
> > API. That is something that will be required for some applications.
> >
> > I need to be able to open sys/clock/foo/something and get a meaningful
> > handle. Sure it's quite likely the operations it supports are related to
> > the POSIX timer ops.
>
> Do you mean this:
>
> id = read(/sys/clock/foo/lock); /* clock is busy, cannot be removed */
That's not for sysfs, if you want to do something like this, create
clockfs please :)
thanks,
greg k-h
next prev parent reply other threads:[~2010-09-11 0:19 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 9:27 [PATCH 0/2] [RFC] posix clock tuning Richard Cochran
2010-09-03 9:29 ` [PATCH 1/2] posix clocks: introduce a syscall for " Richard Cochran
2010-09-03 9:58 ` Richard Cochran
2010-09-04 14:06 ` Richard Cochran
2010-09-09 10:49 ` Thomas Gleixner
2010-09-09 13:34 ` Richard Cochran
2010-09-09 20:10 ` Thomas Gleixner
2010-09-09 21:16 ` Thomas Gleixner
2010-09-09 22:53 ` john stultz
2010-09-10 9:23 ` Richard Cochran
2010-09-09 21:01 ` john stultz
2010-09-09 21:31 ` Thomas Gleixner
2010-09-03 9:30 ` [PATCH 2/2] posix clocks: introduce a sysfs presence Richard Cochran
2010-09-09 22:19 ` john stultz
2010-09-09 23:00 ` Alan Cox
2010-09-10 9:31 ` Richard Cochran
2010-09-11 0:20 ` Greg KH [this message]
2010-09-04 17:23 ` [PATCH 0/2] [RFC] posix clock tuning Christoph Lameter
2010-09-04 17:48 ` Christian Riesch
2010-09-05 1:37 ` Christoph Lameter
2010-09-05 5:56 ` Richard Cochran
2010-09-05 1:47 ` Christoph Lameter
2010-09-05 6:22 ` Richard Cochran
2010-09-05 7:20 ` Richard Cochran
2010-09-05 23:13 ` Christoph Lameter
2010-09-06 7:09 ` Richard Cochran
2010-09-09 9:58 ` Thomas Gleixner
2010-09-09 12:21 ` Richard Cochran
2010-09-09 12:50 ` Thomas Gleixner
2010-09-09 15:02 ` Alan Cox
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=20100911002020.GA20252@kroah.com \
--to=greg@kroah.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.com \
/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