From: "Lu, Yinghai" <yinghai.lu@amd.com>
To: "keith" <kmannth@us.ibm.com>
Cc: "Andi Kleen" <ak@suse.de>, "Matt Tolentino" <metolent@cs.vt.edu>,
akpm@osdl.org, discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: RE: [patch 2/2] add x86-64 support for memory hot-add
Date: Mon, 9 Jan 2006 11:28:19 -0800 [thread overview]
Message-ID: <6F7DA19D05F3CF40B890C7CA2DB13A42030949CF@ssvlexmb2.amd.com> (raw)
I don't know, even yes, according to BKDG, you still need to update
related Routing Table in NB.
YH
-----Original Message-----
From: keith [mailto:kmannth@us.ibm.com]
Sent: Monday, January 09, 2006 11:25 AM
To: Lu, Yinghai
Cc: Andi Kleen; Matt Tolentino; akpm@osdl.org; discuss@x86-64.org;
linux-kernel@vger.kernel.org
Subject: Re: [patch 2/2] add x86-64 support for memory hot-add
On Mon, 2006-01-09 at 10:51 -0800, Yinghai Lu wrote:
> for Opteron NUMA, need to update
> 0. stop the DCT on the node that will plug the new DIMM
> 1. read spd_rom for the added dimm
> 2. init the ram size and update the memory routing table...
> 3. init the timing...
> 4. update relate info in TOM and TOM2, and MTRR, and e820
>
> It looks like we need to get some code about ram init from
LinuxBIOS.....
Is the AMD box not going to use the ACPI add-memory mechanism?
--
keith <kmannth@us.ibm.com>
next reply other threads:[~2006-01-09 19:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 19:28 Lu, Yinghai [this message]
2006-01-09 19:37 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 19:58 Tolentino, Matthew E
2006-01-09 19:55 Tolentino, Matthew E
2006-01-09 20:09 ` keith
2006-01-10 12:34 ` Yasunori Goto
2006-01-10 12:43 ` Yasunori Goto
2006-01-10 12:48 ` Andi Kleen
2006-01-11 1:49 ` Yasunori Goto
2006-01-09 20:27 ` Andi Kleen
2006-01-09 19:29 Lu, Yinghai
2006-01-09 15:21 Matt Tolentino
2006-01-09 15:36 ` Andi Kleen
2006-01-09 18:51 ` Yinghai Lu
2006-01-09 19:24 ` keith
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=6F7DA19D05F3CF40B890C7CA2DB13A42030949CF@ssvlexmb2.amd.com \
--to=yinghai.lu@amd.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=kmannth@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=metolent@cs.vt.edu \
/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
all inboxes | Powered by JetHome®