All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: discuss@x86-64.org, kmannth@us.ibm.com
Cc: lkml <linux-kernel@vger.kernel.org>,
	lhms-devel <lhms-devel@lists.sourceforge.net>,
	andrew <akpm@osdl.org>, dave hansen <haveblue@us.ibm.com>,
	kame <kamezawa.hiroyu@jp.fujitsu.com>, konrad <darnok@us.ibm.com>
Subject: Re: [discuss] [Patch] 2/5 in support of hot-add memory x86_64 create arch_find_node
Date: Sat, 29 Jul 2006 18:25:15 +0200	[thread overview]
Message-ID: <200607291825.16308.ak@suse.de> (raw)
In-Reply-To: <1154141545.5874.146.camel@keithlap>

On Saturday 29 July 2006 04:52, keith mannthey wrote:
>   With the advent of the new ACPI hot-plug memory driver and mechanism
> is needed to deal with ACPI add memory events that do not contain the
> pxm (node) information. I do not believe that the add-event is required
> to contain this information so I create a arch_find_node generic layer
> used in the generic add_memory function.
>
>   If add_memory is called with node < 0 arch_find_node is invoked to
> fine the correct node to add the memory. This created the generic
> construct of arch_find_node.

It would be cleaner to always call add_memory from architecture specific
code instead of such ugly hooks

-Andi

  reply	other threads:[~2006-07-29 16:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-29  2:52 [Patch] 2/5 in support of hot-add memory x86_64 create arch_find_node keith mannthey
2006-07-29 16:25 ` Andi Kleen [this message]
2006-07-29 19:38   ` [discuss] " keith mannthey
2006-07-30  2:17   ` KAMEZAWA Hiroyuki
2006-07-31  7:31     ` [Lhms-devel] " Yasunori Goto

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=200607291825.16308.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=darnok@us.ibm.com \
    --cc=discuss@x86-64.org \
    --cc=haveblue@us.ibm.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kmannth@us.ibm.com \
    --cc=lhms-devel@lists.sourceforge.net \
    --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 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.