public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ulrich Drepper <drepper@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: i2c or eeprom enumeration problem
Date: Sun, 27 Apr 2008 21:20:42 -0700	[thread overview]
Message-ID: <4815509A.9040802@redhat.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On a NUMA system the eeprom interface in /sys

  /sys/bus/i2c/drivers/eeprom/*

do not list all the DRAM eeproms.  Only the DRAM from one node is
listed.  I have a 4 socket system with all 16 banks filled and see only
4 entries.

My suspicion (without looking at any code) is that the list of i2c
devices with eeproms is collected once and this happens only on one CPU.
 I sees not to be dynamic since when I read the files with taskset
restricting execution on certain sockets and cores the result doesn't
change.

Is this known or expected (I hope not the latter)?  Where should I look
at?  I assume that's in the i2c code?

- --
➧ Ulrich Drepper ➧ Red Hat, Inc. ➧ 444 Castro St ➧ Mountain View, CA ❖
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iD8DBQFIFVCa2ijCOnn/RHQRAhA6AJwN9Mc7HzmLM4EgWunC9eucPsDcTwCgtExK
rsz/RJMFHQMB+zIX/WuE2M8=
=OQfT
-----END PGP SIGNATURE-----

             reply	other threads:[~2008-04-28  4:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-28  4:20 Ulrich Drepper [this message]
2008-04-28 12:05 ` i2c or eeprom enumeration problem Andrew Morton
2008-04-28 12:15   ` [i2c] " Jean Delvare
2008-04-28 14:16     ` Ulrich Drepper
2008-04-28 14:21       ` Jean Delvare
2008-04-28 15:27         ` Ulrich Drepper
2008-04-28 16:53           ` Jean Delvare

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=4815509A.9040802@redhat.com \
    --to=drepper@redhat.com \
    --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