From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 on QNAP TS-212 NAS (kw)
Date: Tue, 12 Jul 2011 08:49:04 -0700 [thread overview]
Message-ID: <CAP6exYJ+4HE4K=axuNcjgiocJKnGy8Kk4V+xjRtf_MO2djzytw@mail.gmail.com> (raw)
In-Reply-To: <0e856dc1ce35b2b51ee55663f381c45d@coraid.com>
well, to elaborate on this.
Long ago, you probed by just reading memory until you read back
nothing but ffffffffffffffffff. That was a memory hole. Then somebody
at one chipset vendor got clever and broke this test. Oops, you have
to figure out if maybe your test is failing because somebody got
clever.
You can in fact figure out memory size on many systems by reading
registers in configuration space. On K8/K10/whatever, you can write
code to probe the famous "1f" configuration space and read out memory
bank info. Core 0 can read it for ALL cpus. I've written this and then
lost it :-) but it's pretty easy.
Of course, many vendors view such info as "crown jewels" so this is
hardly a universal solution.
You can, if you want to get really weird, use the I2C bus to probe all
installed DDR and figure it out. Silly that the OS has to do this when
the BIOS does it but hey ... it's a PC ... of course it's gross.
Reference code for MANY chipsets is available in coreboot.
But I agree with Erik: frequently memory slots are more of a headache
than a bonus.
ron
next prev parent reply other threads:[~2011-07-12 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACXGR2Q0bf3dkWGrVT=rkqYrNERe5xdzPuh836CJsbo84A6jVA@mail.gmail.c>
2011-07-09 15:55 ` erik quanstrom
2011-07-09 20:59 ` Jared Jennings
2011-07-09 22:33 ` Jared Jennings
2011-07-10 0:32 ` Jared Jennings
[not found] ` <CACXGR2QsfEkHkfUVu8df+4KeosOLOSVMuAE99ohb-tzY+x9kUQ@mail.gmail.c>
2011-07-10 0:49 ` erik quanstrom
[not found] ` <CACXGR2SCEkWaqEPRZqe7tLgDni6BiEc09MVC-v8puJtUPO7iVQ@mail.gmail.c>
2011-07-09 22:40 ` erik quanstrom
2011-07-12 10:55 ` Ethan Grammatikidis
2011-07-12 15:32 ` erik quanstrom
2011-07-12 15:41 ` Ethan Grammatikidis
2011-07-12 15:49 ` ron minnich [this message]
[not found] ` <CAP6exYJ+4HE4K=axuNcjgiocJKnGy8Kk4V+xjRtf_MO2djzytw@mail.gmail.c>
2011-07-12 16:09 ` erik quanstrom
[not found] ` <CACXGR2QQx=8dxFbJ0Y6eiS5dTgRA2AjpNvzQZOaVOEgt-MFnsw@mail.gmail.c>
2011-07-09 22:31 ` erik quanstrom
2011-07-09 4:38 Jared Jennings
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='CAP6exYJ+4HE4K=axuNcjgiocJKnGy8Kk4V+xjRtf_MO2djzytw@mail.gmail.com' \
--to=rminnich@gmail.com \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).