From: Dave Hansen <haveblue@us.ibm.com>
To: mochel@osdl.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: borked sysfs system devices in 2.5.72
Date: 17 Jun 2003 15:12:09 -0700 [thread overview]
Message-ID: <1055887929.24118.6.camel@nighthawk> (raw)
The per-node numa meminfo files in 2.5.72 are broken, the only display
node0's information. The devices are being properly registered:
Registering sys device 'node0':c0423844 id:0 kobj:c042384c
Registering sys device 'node1':c0423888 id:1 kobj:c0423890
Registering sys device 'node2':c04238cc id:2 kobj:c04238d4
Registering sys device 'node3':c0423910 id:3 kobj:c0423918
When I look at the 4 nodes files with:
"cat /sys/devices/system/node/*/meminfo", I printed out some
information:
subsys_attr_show(kobj: c042384c, attr: c033ea30, page: e76ba000)
subsys_attr_show(kobj: c0423890, attr: c033ea30, page: e76ba000)
subsys_attr_show(kobj: c04238d4, attr: c033ea30, page: e76ba000)
subsys_attr_show(kobj: c0423918, attr: c033ea30, page: e76ba000)
As you can see, the kobj is the one which belongs to the sys device, yet
you do a to_subsys() on it. Why?
struct subsystem * s = to_subsys(kobj);
I'm getting a 0 as the node ID out of pure dumb luck. Is the NUMA code
broken or is sysfs?
--
Dave Hansen
haveblue@us.ibm.com
next reply other threads:[~2003-06-17 21:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 22:12 Dave Hansen [this message]
2003-06-17 22:26 ` borked sysfs system devices in 2.5.72 Patrick Mochel
2003-06-17 22:31 ` Dave Hansen
2003-06-17 22:54 ` Patrick Mochel
2003-06-17 22:58 ` Dave Hansen
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=1055887929.24118.6.camel@nighthawk \
--to=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@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 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.