linux-kernel - Re: i2c or eeprom enumeration problem

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 28 Apr 2008 05:05:15 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Ulrich Drepper <drepper@...hat.com>
Cc:	Linux Kernel <linux-kernel@...r.kernel.org>, i2c@...sensors.org
Subject: Re: i2c or eeprom enumeration problem

On Sun, 27 Apr 2008 21:20:42 -0700 Ulrich Drepper <drepper@...hat.com> wrote:

> -----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?
> 

Let's cc the i2c list.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/