From: Len Brown <lenb@kernel.org>
To: Greg KH <gregkh@suse.de>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH for review] ACPI: Create /sys/firmware/acpi/interrupts/ counters
Date: Tue, 5 Feb 2008 20:58:50 -0500 [thread overview]
Message-ID: <200802052058.50663.lenb@kernel.org> (raw)
In-Reply-To: <20080205231842.GB8740@suse.de>
On Tuesday 05 February 2008 18:18, Greg KH wrote:
> On Tue, Feb 05, 2008 at 06:12:09PM -0500, Len Brown wrote:
> > On Tuesday 05 February 2008 17:18, Greg KH wrote:
> > > On Tue, Feb 05, 2008 at 02:30:10AM -0500, Len Brown wrote:
> > > > # cat /sys/firmware/acpi/interrupts/summary
> > > > pm_timer 0
> > > > glbl_lock 0
> > > > power_btn 0
> > > > sleep_btn 0
> > > > rtc 0
> > > > gpe00 0
> > ...
> > > > gpe1F 0
> > > > gpe_hi 0
> > > > gpe_total 63
> > > > acpi_irq 63
> > >
> > > Eeek! Why? What's wrong with individual files here?
> >
> > My expectation is that this is a shell interface for debugging,
> > not an API for programs. ala /proc/interrupts.
>
> Great, then use debugfs for it. Please, don't put debug stuff like this
> in sysfs, that's not what it is there for. You can do whatever you want
> in debugfs :)
Can you point to a model of good behaviour that I can copy?
note that I want this information to be available on every system,
just like /proc/interrupts is.
/proc/ has seqfile support, is there a reason I shouldn't use it?
I'd banned additional files from /proc/acpi for a long time
since the directory layout was ill-conceived. But maybe I
should re-consider the headlong rush to use sysfs?
thanks,
-Len
next prev parent reply other threads:[~2008-02-06 1:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 7:30 [PATCH for review] ACPI: Create /sys/firmware/acpi/interrupts/ counters Len Brown
2008-02-05 22:18 ` Greg KH
2008-02-05 23:12 ` Len Brown
2008-02-05 23:18 ` Greg KH
2008-02-06 1:58 ` Len Brown [this message]
2008-02-06 2:43 ` Greg KH
2008-02-06 6:33 ` Len Brown
2008-02-06 6:40 ` [PATCH] ACPI: create /sys/firmware/acpi/interrupts/ (v2) Len Brown
2008-02-07 0:16 ` Greg KH
2008-02-06 6:49 ` [PATCH for review] ACPI: Create /sys/firmware/acpi/interrupts/ counters Greg KH
2008-02-06 0:44 ` Bjorn Helgaas
2008-02-06 1:53 ` Len Brown
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=200802052058.50663.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=gregkh@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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