From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Renninger <trenn@suse.de>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Felix Schnizlein <fschnizlein@suse.com>,
linux-kernel@vger.kernel.org,
Felix Schnizlein <fschnizlein@suse.de>,
linux-arch@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux@armlinux.org.uk, will.deacon@arm.com, x86@kernel.org
Subject: Re: [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86
Date: Wed, 11 Dec 2019 14:56:19 +0100 [thread overview]
Message-ID: <20191211135619.GA538980@kroah.com> (raw)
In-Reply-To: <4737004.4U1sY2OxSp@skinner.arch.suse.de>
On Wed, Dec 11, 2019 at 11:42:35AM +0100, Thomas Renninger wrote:
> If Greg (and others) are ok, I would add "page size exceeding" handling.
> Hm, quick searching for an example I realize that debugfs can exceed page
> size. Is it that hard to expose a sysfs file larger than page size?
No, there is a simple way to do it, but I'm not going to show you how as
it is NOT how to use sysfs at all :)
Why are you wanting to dump this whole mess into one file and then parse
it, it's no different from having 100+ different sysfs files and then
doing a readdir(3) on the thing, right?
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Thomas Renninger <trenn@suse.de>
Cc: linux-arch@vger.kernel.org,
Felix Schnizlein <fschnizlein@suse.de>,
Felix Schnizlein <fschnizlein@suse.com>,
x86@kernel.org, will.deacon@arm.com,
linux-kernel@vger.kernel.org, linux@armlinux.org.uk,
Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86
Date: Wed, 11 Dec 2019 14:56:19 +0100 [thread overview]
Message-ID: <20191211135619.GA538980@kroah.com> (raw)
In-Reply-To: <4737004.4U1sY2OxSp@skinner.arch.suse.de>
On Wed, Dec 11, 2019 at 11:42:35AM +0100, Thomas Renninger wrote:
> If Greg (and others) are ok, I would add "page size exceeding" handling.
> Hm, quick searching for an example I realize that debugfs can exceed page
> size. Is it that hard to expose a sysfs file larger than page size?
No, there is a simple way to do it, but I'm not going to show you how as
it is NOT how to use sysfs at all :)
Why are you wanting to dump this whole mess into one file and then parse
it, it's no different from having 100+ different sysfs files and then
doing a readdir(3) on the thing, right?
greg k-h
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-12-11 13:56 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 16:24 [PATCH v5 0/3] sysfs: add sysfs based cpuinfo Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:24 ` [PATCH 1/3] cpuinfo: add sysfs based arch independent cpuinfo framework Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:33 ` Greg KH
2019-12-06 16:33 ` Greg KH
2019-12-06 16:33 ` Greg KH
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:56 ` Randy Dunlap
2019-12-06 16:24 ` [PATCH 2/3] x86 cpuinfo: implement sysfs nodes for x86 Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:36 ` Greg KH
2019-12-06 16:36 ` Greg KH
2019-12-10 20:48 ` Thomas Gleixner
2019-12-10 20:48 ` Thomas Gleixner
2019-12-10 20:53 ` Greg KH
2019-12-10 20:53 ` Greg KH
2019-12-11 10:42 ` Thomas Renninger
2019-12-11 10:42 ` Thomas Renninger
2019-12-11 13:56 ` Greg KH [this message]
2019-12-11 13:56 ` Greg KH
2019-12-11 14:12 ` Thomas Renninger
2019-12-11 14:12 ` Thomas Renninger
2019-12-11 14:26 ` Greg KH
2019-12-11 14:26 ` Greg KH
2019-12-11 14:52 ` Thomas Renninger
2019-12-11 14:52 ` Thomas Renninger
2019-12-11 14:57 ` Greg KH
2019-12-11 14:57 ` Greg KH
2019-12-06 16:24 ` [PATCH 3/3] arm64 cpuinfo: implement sysfs nodes for arm64 Thomas Renninger
2019-12-06 16:24 ` Thomas Renninger
2019-12-06 16:37 ` Greg KH
2019-12-06 16:37 ` Greg KH
2019-12-09 10:31 ` Will Deacon
2019-12-09 10:31 ` Will Deacon
2019-12-09 11:28 ` Thomas Renninger
2019-12-09 11:28 ` Thomas Renninger
2019-12-09 17:38 ` Will Deacon
2019-12-09 17:38 ` Will Deacon
2019-12-10 13:33 ` Thomas Renninger
2019-12-10 13:33 ` Thomas Renninger
2019-12-10 14:47 ` Greg KH
2019-12-10 14:47 ` Greg KH
2019-12-10 16:24 ` Thomas Renninger
2019-12-10 16:24 ` Thomas Renninger
2019-12-06 16:58 ` [PATCH v5 0/3] sysfs: add sysfs based cpuinfo Mark Rutland
2019-12-06 16:58 ` Mark Rutland
2019-12-06 17:29 ` Thomas Renninger
2019-12-06 17:29 ` Thomas Renninger
2019-12-06 18:16 ` Mark Rutland
2019-12-06 18:16 ` Mark Rutland
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=20191211135619.GA538980@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fschnizlein@suse.com \
--cc=fschnizlein@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=tglx@linutronix.de \
--cc=trenn@suse.de \
--cc=will.deacon@arm.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.